Skip to main content
Glama

tavily-map

Create structured website maps to analyze site architecture, discover content, and audit navigation paths for better understanding of web structure.

Instructions

A powerful web mapping tool that creates a structured map of website URLs, allowing you to discover and analyze site structure, content organization, and navigation paths. Perfect for site audits, content discovery, and understanding website architecture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe root URL to begin the mapping
max_depthNoMax depth of the mapping. Defines how far from the base URL the crawler can explore
max_breadthNoMax number of links to follow per level of the tree (i.e., per page)
limitNoTotal number of links the crawler will process before stopping
instructionsNoNatural language instructions for the crawler
select_pathsNoRegex patterns to select only URLs with specific path patterns (e.g., /docs/.*, /api/v1.*)
select_domainsNoRegex patterns to select crawling to specific domains or subdomains (e.g., ^docs\.example\.com$)
allow_externalNoWhether to allow following links that go to external domains
categoriesNoFilter URLs using predefined categories like documentation, blog, api, etc

Implementation Reference

  • Core handler function that implements the tavily-map tool by making a POST request to the Tavily API's map endpoint with user parameters and handling errors.
    async map(params: any): Promise<TavilyMapResponse> {
      try {
        const response = await this.axiosInstance.post(this.baseURLs.map, {
          ...params,
          api_key: API_KEY
        });
        return response.data;
      } catch (error: any) {
        if (error.response?.status === 401) {
          throw new Error('Invalid API key');
        } else if (error.response?.status === 429) {
          throw new Error('Usage limit exceeded');
        }
        throw error;
      }
    }
  • src/index.ts:285-346 (registration)
    Registration of the tavily-map tool in the ListToolsRequestSchema handler, defining its name, description, and input schema for validation.
    {
      name: "tavily-map",
      description: "A powerful web mapping tool that creates a structured map of website URLs, allowing you to discover and analyze site structure, content organization, and navigation paths. Perfect for site audits, content discovery, and understanding website architecture.",
      inputSchema: {
        type: "object",
        properties: {
          url: { 
            type: "string", 
            description: "The root URL to begin the mapping"
          },
          max_depth: {
            type: "integer",
            description: "Max depth of the mapping. Defines how far from the base URL the crawler can explore",
            default: 1,
            minimum: 1
          },
          max_breadth: {
            type: "integer",
            description: "Max number of links to follow per level of the tree (i.e., per page)",
            default: 20,
            minimum: 1
          },
          limit: {
            type: "integer",
            description: "Total number of links the crawler will process before stopping",
            default: 50,
            minimum: 1
          },
          instructions: {
            type: "string",
            description: "Natural language instructions for the crawler"
          },
          select_paths: {
            type: "array",
            items: { type: "string" },
            description: "Regex patterns to select only URLs with specific path patterns (e.g., /docs/.*, /api/v1.*)",
            default: []
          },
          select_domains: {
            type: "array",
            items: { type: "string" },
            description: "Regex patterns to select crawling to specific domains or subdomains (e.g., ^docs\\.example\\.com$)",
            default: []
          },
          allow_external: {
            type: "boolean",
            description: "Whether to allow following links that go to external domains",
            default: false
          },
          categories: {
            type: "array",
            items: { 
              type: "string",
              enum: ["Careers", "Blog", "Documentation", "About", "Pricing", "Community", "Developers", "Contact", "Media"]
            },
            description: "Filter URLs using predefined categories like documentation, blog, api, etc",
            default: []
          }
        },
        required: ["url"]
      }
    },
  • Dispatch case in the CallToolRequestSchema handler that invokes the tavily-map implementation with arguments and formats the response.
    case "tavily-map":
      const mapResponse = await this.map({
        url: args.url,
        max_depth: args.max_depth,
        max_breadth: args.max_breadth,
        limit: args.limit,
        instructions: args.instructions,
        select_paths: Array.isArray(args.select_paths) ? args.select_paths : [],
        select_domains: Array.isArray(args.select_domains) ? args.select_domains : [],
        allow_external: args.allow_external,
        categories: Array.isArray(args.categories) ? args.categories : []
      });
      return {
        content: [{
          type: "text",
          text: formatMapResults(mapResponse)
        }]
      };
  • Supporting helper function that formats the TavilyMapResponse into a readable text output for the tool response.
    function formatMapResults(response: TavilyMapResponse): string {
      const output: string[] = [];
      
      output.push(`Site Map Results:`);
      output.push(`Base URL: ${response.base_url}`);
      
      output.push('\nMapped Pages:');
      response.results.forEach((page, index) => {
        output.push(`\n[${index + 1}] URL: ${page}`);
      });
      
      return output.join('\n');
    }
  • TypeScript interface defining the expected response schema from the Tavily map API.
    interface TavilyMapResponse {
      base_url: string;
      results: string[];
      response_time: number;
    }
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. While it mentions the tool is 'powerful' and for 'analysis,' it doesn't describe key behavioral traits such as rate limits, authentication requirements, potential impacts on target websites (e.g., crawling load), or what the output looks like (e.g., structured data format). This leaves significant gaps for a tool with 9 parameters and no output schema.

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

Conciseness4/5

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

The description is appropriately sized with two sentences: the first states the core functionality, and the second lists use cases. It's front-loaded with the main purpose and avoids unnecessary fluff, though the phrase 'Perfect for' could be slightly more formal. Overall, it's efficient and well-structured.

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

Completeness2/5

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

Given the tool's complexity (9 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain behavioral aspects like crawling behavior, output format, or error handling, which are critical for an agent to use it effectively. The lack of annotations and output schema means the description should compensate more, but it falls short, leaving key operational details unspecified.

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?

Schema description coverage is 100%, so the schema already documents all 9 parameters thoroughly. The description adds no specific parameter semantics beyond implying general mapping behavior (e.g., 'discover and analyze site structure'), which doesn't provide additional details beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'creates a structured map of website URLs' for 'discover and analyze site structure, content organization, and navigation paths.' It specifies the verb ('creates a structured map') and resource ('website URLs'), but doesn't explicitly differentiate from sibling tools like 'tavily-crawl' or 'tavily-extract' beyond mentioning it's for mapping and analysis.

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 contexts ('Perfect for site audits, content discovery, and understanding website architecture'), providing some guidance on when to use it. However, it doesn't explicitly state when not to use it or name alternatives like 'tavily-crawl' for different crawling needs, leaving the agent to infer appropriate usage scenarios.

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/jackedelic/tavily-mcp'

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