Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

by ravinwebsurgeon
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

dataforseo_labs_google_historical_rank_overview

Analyze historical SEO performance by tracking domain ranking distribution in SERPs and estimating monthly organic and paid traffic volume over time.

Instructions

This endpoint will provide you with historical data on rankings and traffic of the specified domain, such as domain ranking distribution in SERPs and estimated monthly traffic volume for both organic and paid results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYestarget domain
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
include_clickstream_dataNoInclude or exclude data from clickstream-based metrics in the result

Implementation Reference

  • src/core/modules/dataforseo-labs/tools/google/competitor-research/google-historical-domain-rank-overview.tool.ts:38-52 (handler)
    The handle method executes the tool logic by making a POST request to the DataForSEO Labs API for Google historical domain rank overview.
    async handle(params: any): Promise<any> {
  try {
    const response = await this.client.makeRequest('/v3/dataforseo_labs/google/historical_rank_overview/live', 'POST', [{
      target: params.target,
      location_name: params.location_name,
      language_code: params.language_code,
      ignore_synonyms: params.ignore_synonyms,
      include_clickstream_data: params.include_clickstream_data
    }]);
    return this.validateAndFormatResponse(response);

  } catch (error) {
    return this.formatErrorResponse(error);
  }
}
  • src/core/modules/dataforseo-labs/tools/google/competitor-research/google-historical-domain-rank-overview.tool.ts:18-36 (schema)
    Input schema definition using Zod for the tool parameters.
      getParams(): z.ZodRawShape {
    return {
      target: z.string().describe(`target domain`),
      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`),        
      include_clickstream_data: z.boolean().optional().default(false).describe(
        `Include or exclude data from clickstream-based metrics in the result`)
    };
  }
  • src/core/modules/dataforseo-labs/dataforseo-labs-api.module.ts:18-18 (registration)
    Import statement for the GoogleHistoricalDomainRankOverviewTool class.
    import { GoogleHistoricalDomainRankOverviewTool } from './tools/google/competitor-research/google-historical-domain-rank-overview.tool.js';
  • src/core/modules/dataforseo-labs/dataforseo-labs-api.module.ts:46-46 (registration)
    Instantiation and registration of the tool instance in the module's getTools() method.
    new GoogleHistoricalDomainRankOverviewTool(this.dataForSEOClient),
  • src/core/modules/dataforseo-labs/tools/labs-filters.tool.ts:34-34 (helper)
    Mapping of the tool name to its filter path in the labs filters tool.
    'dataforseo_labs_google_historical_rank_overview': 'domain_rank_overview.google',

Tool Definition Quality

C2.9/5.0
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 the tool provides 'historical data' and examples of data types, but lacks critical behavioral details: it doesn't specify if this is a read-only operation, potential rate limits, authentication requirements, data freshness, or error conditions. For a data retrieval tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, well-structured sentence that efficiently conveys the core functionality without unnecessary words. It's front-loaded with the main purpose and includes specific examples, making it easy to parse. However, it could be slightly more concise by avoiding the phrase 'such as' redundancy.

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 complexity (5 parameters, no annotations, no output schema), the description is incomplete. It adequately explains what the tool does but fails to address key contextual aspects: no guidance on usage versus siblings, no behavioral transparency (e.g., read-only status, rate limits), and no details on output format or error handling. For a tool with rich parameters and no structured safety hints, more comprehensive description is needed.

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%, meaning all parameters are documented in the schema itself. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain the 'target' domain format or clarify 'include_clickstream_data' implications). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description could have enhanced understanding with practical examples.

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 historical data on rankings and traffic of the specified domain' with specific examples like 'domain ranking distribution in SERPs and estimated monthly traffic volume for both organic and paid results'. It uses specific verbs ('provide') and resources ('historical data', 'rankings', 'traffic'), though it doesn't explicitly differentiate from sibling tools like 'dataforseo_labs_google_domain_rank_overview' which might offer similar functionality.

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. It doesn't mention any prerequisites, exclusions, or comparisons to sibling tools (e.g., 'dataforseo_labs_google_domain_rank_overview' or 'dataforseo_labs_google_historical_serp'), leaving the agent to infer usage context solely from the tool name and description.

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