tavily-automation

Tavily Automation - Automating Tavily Search Tasks via Rube MCP

Skill Overview

Tavily Automation is a skill that integrates the Composio Tavily toolkit through Rube MCP. It helps you dynamically discover and execute Tavily Search API operations in MCP clients such as Claude Code, without manually managing API keys or hardcoding tool schemas.

Applicable Scenarios

1. Integrating Search Capabilities into AI Agents

When your AI application needs real-time search capabilities, this skill enables dynamic calls to various Tavily search tools, including standard search, deep search, and academic search. Tool schemas are updated automatically, eliminating the need to maintain API call code.

2. Automating Search Tasks in Claude Code

When you need to perform web searches or information retrieval tasks during a Claude Code session, use RUBE_MULTI_EXECUTE_TOOL to orchestrate multiple Tavily tool calls in a single operation, with session management and schema validation handled automatically.

3. Batch Searching and Data Processing

When you need to perform batch searches, comparisons, or aggregated analyses across multiple queries, use RUBE_REMOTE_WORKBENCH to execute run_composio_tool() for batch operations and automatically handle paginated results.

Core Features

Dynamic Tool Discovery

Use RUBE_SEARCH_TOOLS to obtain the current schemas, input parameters, recommended execution plans, and known pitfalls for Tavily tools in real time. This helps prevent call failures caused by tool updates. Tool schemas may change with the Composio platform, so searching before each execution ensures compatibility.

Automated Connection Management

Use RUBE_MANAGE_CONNECTIONS to verify the status of the Tavily connection. If it is not active, an authentication link will be returned automatically. Simply add the https://rube.app/mcp endpoint through Rube MCP to get started, without storing API keys in your code.

Flexible Tool Execution

Supports single-tool execution (RUBE_MULTI_EXECUTE_TOOL), batch operations through the Remote Workbench (RUBE_REMOTE_WORKBENCH), and retrieving complete schemas (RUBE_GET_TOOL_SCHEMAS). A session ID can be reused within a single workflow; generate a new ID across workflows to maintain isolation.

Frequently Asked Questions

What Is Rube MCP, and Why Is It Needed?

Rube MCP (rube.app/mcp) is an MCP server endpoint that provides unified access to the Composio tool ecosystem. Through Rube MCP, you can dynamically manage and execute various third-party tools, including Tavily, using tools such as RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL. Rube MCP eliminates the need to manage API keys directly in your code; all authentication is handled through the connection management process.

Why Must RUBE_SEARCH_TOOLS Be Called First?

Tool schemas on the Composio platform may be updated at any time. Hardcoding tool slugs or parameter structures can lead to call failures. RUBE_SEARCH_TOOLS returns the current tool list, input schemas, recommended execution plans, and known pitfalls, ensuring that your calls match the platform’s current state. This is the core principle behind “Always search tools first for current schemas.”

How Can I Verify That the Tavily Connection Is Working Properly?

Call RUBE_MANAGE_CONNECTIONS with toolkits: ["tavily"] and your session_id. If the returned connection status is not ACTIVE, complete the authentication process using the returned auth_link. After authentication, call it again to confirm that the status is ACTIVE before starting tool calls. It is recommended to check the connection status at the beginning of each workflow.