Zyte API Automation

What This Skill Does

The Zyte API Automation skill enables users to automate Zyte API operations through Composio's Zyte API toolkit via Rube MCP. It is designed for developers and data engineers who need to programmatically interact with the Zyte API. The skill simplifies tool discovery, connection management, and execution of Zyte API tasks.

When to Use

• Automate web scraping tasks using Zyte API.
• Extract data from websites programmatically.
• Monitor website content changes.
• Integrate Zyte API with data pipelines.
• Schedule recurring data extraction jobs.
• Automate data validation using Zyte API.

Key Features

• Automates Zyte API operations via Rube MCP.
• Uses Composio's Zyte API toolkit.
• Discovers available Zyte API tools.
• Manages Zyte API connections.
• Executes Zyte API tools with schema-compliant arguments.
• Provides a structured workflow for Zyte API automation.

Manual Installation

Zyte API Automation via Rube MCP

Automate Zyte API operations through Composio's Zyte API toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/zyte_api

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Zyte API connection via RUBE_MANAGE_CONNECTIONS with toolkit zyte_api Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit zyte_api If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Zyte API operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Zyte API task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["zyte_api"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Zyte API Automation via Rube MCP

Automate Zyte API operations through Composio's Zyte API toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/zyte_api

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Zyte API task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["zyte_api"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference