Skip to main content
Glama
sumitchatterjee13

Tavily Cursor MCP Server

tavily_extract

Extract clean content from web pages by removing ads and navigation elements. Use this tool to retrieve main content from multiple URLs for research or analysis.

Instructions

Extract clean content from one or more URLs. Returns the main content from web pages, removing ads and navigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesArray of URLs to extract content from

Implementation Reference

  • Handler for the tavily_extract tool: calls tavilyClient.extract with the provided URLs and returns the JSON result as text content.
    case "tavily_extract": {
      const result = await tavilyClient.extract({
        urls: args.urls,
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • index.js:135-152 (registration)
    Registration of the tavily_extract tool in the ListTools response, including name, description, and input schema.
    {
      name: "tavily_extract",
      description:
        "Extract clean content from one or more URLs. Returns the main content from web pages, removing ads and navigation.",
      inputSchema: {
        type: "object",
        properties: {
          urls: {
            type: "array",
            items: {
              type: "string",
            },
            description: "Array of URLs to extract content from",
          },
        },
        required: ["urls"],
      },
    },
  • Input schema definition for the tavily_extract tool.
    inputSchema: {
      type: "object",
      properties: {
        urls: {
          type: "array",
          items: {
            type: "string",
          },
          description: "Array of URLs to extract content from",
        },
      },
      required: ["urls"],
    },
  • TavilyClient.extract method: performs the HTTP POST to Tavily's /extract endpoint with API key and parameters.
    async extract(params) {
      const response = await fetch(`${this.baseUrl}/extract`, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
        },
        body: JSON.stringify({
          api_key: this.apiKey,
          ...params,
        }),
      });
    
      if (!response.ok) {
        throw new Error(`Tavily API error: ${response.statusText}`);
      }
    
      return await response.json();
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that content is 'clean' with ads and navigation removed, which adds some context, but lacks details on error handling, rate limits, authentication needs, or output format. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core purpose and followed by a clarifying detail. Every sentence earns its place by specifying the action, resource, and behavioral outcome without redundancy or unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (extracting content from URLs) and lack of annotations and output schema, the description is partially complete. It covers the purpose and basic behavior but omits details on output structure, error cases, and usage constraints, which are important for effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'urls' parameter documented as 'Array of URLs to extract content from'. The description adds no additional meaning beyond this, such as URL format requirements or limits on array size. With high schema coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Extract clean content') and resource ('from one or more URLs'), with explicit mention of what is extracted ('main content from web pages') and what is removed ('ads and navigation'). It distinguishes from sibling tools (tavily_search, tavily_search_context, tavily_search_qna) by focusing on extraction rather than search or Q&A functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for extracting main content from URLs, but does not explicitly state when to use this tool versus alternatives like the sibling search tools. No guidance is provided on exclusions or prerequisites, such as URL validity or content type limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sumitchatterjee13/tavily-cursor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server