Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

domain_analytics_whois_overview

Retrieve Whois data enriched with backlink statistics, ranking information, and traffic metrics from organic and paid search results for specified domains.

Instructions

This endpoint will provide you with Whois data enriched with backlink stats, and ranking and traffic info from organic and paid search results. Using this endpoint you will be able to get all these data for the domains matching the parameters you specify in the request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNothe maximum number of returned domains
offsetNooffset in the results array of returned businesses optional field default value: 0 if you specify the 10 value, the first ten entities in the results array will be omitted and the data will be provided for the successive entities
filtersNoarray of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, <, <=, >, >=, =, <>, in, not_in, like, not_like, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: ["rating.value",">",3]
order_byNoresults sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting parameter example: ["rating.value,desc"]note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["rating.value,desc","rating.votes_count,desc"]
is_claimedNoindicates whether the business is verified by its owner on Google Maps

Implementation Reference

  • The main handler function that executes the tool logic: formats parameters, makes POST request to DataForSEO API endpoint '/v3/domain_analytics/whois/overview/live', validates and formats response or error.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/domain_analytics/whois/overview/live', 'POST', [{        
          limit: params.limit,
          offset: params.offset,
          filters: this.formatFilters(params.filters),
          order_by: this.formatOrderBy(params.order_by),
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Input schema validation using Zod for tool parameters: limit, offset, filters, order_by, is_claimed.
      getParams(): z.ZodRawShape {
        return {
          limit: z.number().min(1).max(1000).default(10).optional().describe("the maximum number of returned domains"),
          offset: z.number().min(0).optional().describe(
            `offset in the results array of returned businesses
    optional field
    default value: 0
    if you specify the 10 value, the first ten entities in the results array will be omitted and the data will be provided for the successive entities`
          ),
          filters: z.array(
            z.union([
              z.array(z.union([z.string(), z.number(), z.boolean()])).length(3),
              z.enum(["and", "or"])
            ])
          ).max(8).optional().describe(
            `array of results filtering parameters
    optional field
    you can add several filters at once (8 filters maximum)
    you should set a logical operator and, or between the conditions
    the following operators are supported:
    regex, not_regex, <, <=, >, >=, =, <>, in, not_in, like, not_like, match, not_match
    you can use the % operator with like and not_like to match any string of zero or more characters
    example:
    ["rating.value",">",3]`
          ),
          order_by: z.array(z.string()).optional().describe(
            `results sorting rules
    optional field
    you can use the same values as in the filters array to sort the results
    possible sorting types:
    asc – results will be sorted in the ascending order
    desc – results will be sorted in the descending order
    you should use a comma to set up a sorting parameter
    example:
    ["rating.value,desc"]note that you can set no more than three sorting rules in a single request
    you should use a comma to separate several sorting rules
    example:
    ["rating.value,desc","rating.votes_count,desc"]`
          ),
          is_claimed: z.boolean().optional().describe(`indicates whether the business is verified by its owner on Google Maps`).default(true)
        };
      }
  • Tool registration in DomainAnalyticsApiModule's getTools() method: instantiates WhoisOverviewTool and registers it with name, description, params, and handler reference.
    getTools(): Record<string, ToolDefinition> {
      const tools = [
        new WhoisOverviewTool(this.dataForSEOClient),
        new WhoisFiltersTool(this.dataForSEOClient),
        new DomainTechnologiesTool(this.dataForSEOClient),
        new DomainTechnologiesFiltersTool(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),
        },
      }), {});
    }
  • Helper mapping in WhoisFiltersTool that associates the tool name with its filter path 'overview' for filter handling.
    private static readonly TOOL_TO_FILTER_MAP: { [key: string]: string } = {
      'domain_analytics_whois_overview': 'overview'
    };
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 describes what data is returned but doesn't mention critical behaviors like rate limits, authentication needs, pagination (beyond limit/offset parameters), error handling, or whether it's a read-only or mutating operation. For a tool with complex filtering and sorting, 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 concise and front-loaded, with two sentences that directly state the tool's purpose and usage. There's no wasted verbiage, and it efficiently communicates the core functionality. However, it could be slightly more structured by explicitly separating purpose from usage instructions.

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 (5 parameters with rich filtering/sorting logic), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects, output format, error conditions, or usage context. While the schema covers parameters well, the description fails to compensate for other gaps, making it inadequate for informed tool selection.

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 adds no additional parameter semantics beyond implying that parameters filter domains. It doesn't explain the meaning or typical use of 'filters' or 'order_by' 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: 'provide you with Whois data enriched with backlink stats, and ranking and traffic info from organic and paid search results.' It specifies the verb ('provide'), resource ('Whois data'), and additional enriched data. However, it doesn't explicitly differentiate from sibling tools like 'domain_analytics_whois_available_filters' or other domain analytics tools, which would require a 5.

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 'domains matching the parameters you specify' but doesn't clarify use cases, prerequisites, or comparisons to sibling tools like 'domain_analytics_technologies_domain_technologies' or 'backlinks_domain_pages'. This lack of contextual guidance limits its utility for an AI agent.

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