Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

dataforseo_labs_bulk_traffic_estimation

Estimate monthly organic, paid, featured snippet, and local pack traffic for up to 1,000 domains or pages to analyze search performance.

Instructions

This endpoint will provide you with estimated monthly traffic volumes for up to 1,000 domains, subdomains, or webpages. Along with organic search traffic estimations, you will also get separate values for paid search, featured snippet, and local pack results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetsYestarget domains, subdomains, and webpages. you can specify domains, subdomains, and webpages in this field; domains and subdomains should be specified without https:// and www.; pages should be specified with absolute URL, including https:// and www.; you can set up to 1000 domains, subdomains or webpages
location_nameNofull name of the location required field only in format "Country" (not "City" or "Region") example: 'United Kingdom', 'United States', 'Canada'United States
language_codeNolanguage code required field example: enen
ignore_synonymsNoignore highly similar keywords, if set to true, results will be more accurate
item_typesNodisplay results by item type indicates the type of search results included in the response

Implementation Reference

  • Executes the tool by sending a POST request to DataForSEO Labs API for bulk traffic estimation on specified targets, with location, language, and synonym settings.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/dataforseo_labs/google/bulk_traffic_estimation/live', 'POST', [{
          targets: params.targets,
          location_name: params.location_name,
          language_code: params.language_code,
          item_types: ['organic'],
          ignore_synonyms: params.ignore_synonyms
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema defining the input parameters: targets (array of strings), location_name, language_code, ignore_synonyms.
      getParams(): z.ZodRawShape {
        return {
          targets: z.array(z.string()).describe(`target domains, subdomains, and webpages.
            you can specify domains, subdomains, and webpages in this field;
    domains and subdomains should be specified without https:// and www.;
    pages should be specified with absolute URL, including https:// and www.;
    you can set up to 1000 domains, subdomains or webpages`),
          location_name: z.string().default("United States").describe(`full name of the location
    required field
    in format "Country"
    example:
    United Kingdom`),
          language_code: z.string().default("en").describe(
            `language code
            required field
            example:
            en`),
          ignore_synonyms: z.boolean().default(true).describe(
      `ignore highly similar keywords, if set to true, results will be more accurate`),
    
        };
      }
  • Registers the GoogleBulkTrafficEstimationTool instance in the DataForSEOLabsApi module's getTools() method, mapping it by name to its description, params, and handler.
    getTools(): Record<string, ToolDefinition> {
      const tools = [
        new GoogleRankedKeywordsTool(this.dataForSEOClient),
        new GoogleDomainCompetitorsTool(this.dataForSEOClient),
        new GoogleDomainRankOverviewTool(this.dataForSEOClient),
        new GoogleKeywordsIdeasTool(this.dataForSEOClient),
        new GoogleRelatedKeywordsTool(this.dataForSEOClient),
        new GoogleKeywordsSuggestionsTool(this.dataForSEOClient),
        new GoogleHistoricalSERP(this.dataForSEOClient),
        new GoogleSERPCompetitorsTool(this.dataForSEOClient),
        new GoogleBulkKeywordDifficultyTool(this.dataForSEOClient),
        new GoogleSubdomainsTool(this.dataForSEOClient),
        new GoogleKeywordOverviewTool(this.dataForSEOClient),
        new GoogleTopSearchesTool(this.dataForSEOClient),
        new GoogleSearchIntentTool(this.dataForSEOClient),
        new GoogleKeywordsForSiteTool(this.dataForSEOClient),
        new GoogleDomainIntersectionsTool(this.dataForSEOClient),
        new GoogleHistoricalDomainRankOverviewTool(this.dataForSEOClient),
        new GooglePageIntersectionsTool(this.dataForSEOClient),
        new GoogleBulkTrafficEstimationTool(this.dataForSEOClient),
        new DataForSeoLabsFilterTool(this.dataForSEOClient),
        new GoogleHistoricalKeywordDataTool(this.dataForSEOClient),
        // Add more tools here
      ];
    
      return tools.reduce((acc, tool) => ({
        ...acc,
        [tool.getName()]: {
          description: tool.getDescription(),
          params: tool.getParams(),
          handler: (params: any) => tool.handle(params),
        },
      }), {});
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool provides 'estimated monthly traffic volumes' and lists traffic types (organic, paid, featured snippet, local pack), but doesn't disclose important behavioral aspects like rate limits, data freshness, accuracy limitations, authentication requirements, or whether this is a read-only operation. The description is insufficient for a tool with no annotation coverage.

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 efficiently structured in two sentences that convey the core functionality and traffic breakdown. It's appropriately sized without unnecessary elaboration, though it could be slightly more front-loaded by mentioning the bulk capability earlier. Every sentence contributes meaningful information.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the output looks like (structure, units, confidence intervals), doesn't mention performance characteristics (speed, limitations), and provides minimal behavioral context. The description should do more to compensate for the lack of structured metadata.

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 5 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema - it mentions 'domains, subdomains, or webpages' which aligns with the 'targets' parameter but provides no additional semantic context. 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: 'provide you with estimated monthly traffic volumes for up to 1,000 domains, subdomains, or webpages' with specific traffic types listed. It uses a specific verb ('provide') and resource ('traffic volumes'), but doesn't explicitly differentiate from sibling tools like 'dataforseo_labs_google_domain_rank_overview' or 'dataforseo_labs_google_historical_rank_overview' that might also provide traffic-related data.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. While it mentions the tool handles 'up to 1,000 domains, subdomains, or webpages,' it doesn't indicate when bulk estimation is preferable over individual domain tools, nor does it reference any sibling tools for comparison. There are no usage prerequisites or exclusions mentioned.

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/ravinwebsurgeon/seo-mcp'

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