Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

dataforseo_labs_google_domain_rank_overview

Analyze domain ranking distribution and estimated monthly traffic from organic and paid search results for SEO performance evaluation.

Instructions

This endpoint will provide you with ranking and traffic data from organic and paid search for the specified domain. You will be able to review the domain ranking distribution in SERPs as well as 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

Implementation Reference

  • The handler function that executes the core tool logic by making a POST request to the DataForSEO Labs API endpoint '/v3/dataforseo_labs/google/domain_rank_overview/live' using the provided input parameters.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/dataforseo_labs/google/domain_rank_overview/live', 'POST', [{
          target: params.target,
          location_name: params.location_name,
          language_code: params.language_code,
          ignore_synonyms: params.ignore_synonyms
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema defining the input parameters: target (domain), location_name, language_code, ignore_synonyms.
      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`)
        };
      }
  • Instantiation and registration of the GoogleDomainRankOverviewTool in the DataForSEOLabsApi module's getTools() method, which returns a record of all tools including this one mapped by name.
    new GoogleDomainRankOverviewTool(this.dataForSEOClient),
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. It states the tool provides data but doesn't disclose behavioral traits such as whether it's a read-only operation, requires authentication, has rate limits, or involves data freshness/latency. The description is vague about what 'estimated monthly traffic volume' entails and doesn't mention potential costs or limitations.

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 concise with two sentences that directly state the tool's function. It's front-loaded with the core purpose and avoids unnecessary details. However, it could be slightly more structured by explicitly separating organic vs. paid data aspects.

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 of SEO/ranking data and lack of annotations or output schema, the description is incomplete. It doesn't explain the format or structure of returned data (e.g., metrics, timeframes), potential errors, or how to interpret 'ranking distribution in SERPs.' For a data retrieval tool with no output schema, more context is needed for effective use.

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 four parameters thoroughly. The description adds no parameter-specific information beyond implying the 'target' parameter is a domain. It doesn't explain how parameters interact or affect results, so it meets the baseline but adds minimal value.

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 ranking and traffic data from organic and paid search for the specified domain.' It specifies the verb ('provide') and resource ('ranking and traffic data'), and mentions the domain scope. However, it doesn't explicitly differentiate from sibling tools like 'dataforseo_labs_google_historical_rank_overview' or 'dataforseo_labs_google_ranked_keywords', which likely have overlapping 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 mentions what data is provided but doesn't specify use cases, prerequisites, or comparisons to sibling tools. For example, it doesn't clarify if this is for current vs. historical data or how it differs from other domain ranking tools in the list.

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