SE Ranking SEO Data API MCP Server

Domain Overview DB

domainOverviewDb

Get domain overview and keyword statistics from a selected regional SEO database by entering a domain and country code; optionally include subdomains in the analysis.

Instructions

Fetch domain overview by database (v1/domain/overview/db)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>",
      "domain": "<domain>"
    },
    "name": "domainOverviewDb"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	The domain for which to retrieve the keyword statistics.
`source`	Yes	Alpha-2 country code of the regional keyword database.
`with_subdomains`	No	A flag to determine whether data for subdomains should be included in the analysis.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

C2.8/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. 'Fetch' implies a read-only operation, but the description does not explain how the regional database selection works, what data is returned, whether authentication is required, or how with_subdomains alters the behavior. The endpoint string adds minimal behavioral context.

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

Conciseness3/5

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

The description is a single concise sentence with no wasted words, which is good. However, it is so terse that it borders on under-specification, and the endpoint path largely restates the tool name rather than adding useful structural context.

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 no output schema and no annotations, the description should explain what 'by database' means, how it differs from sibling tools, and what the response contains. It only names the operation; the schema covers parameters but not the contextual behavior needed for correct selection and invocation.

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 three parameters. The description adds little beyond the schema; 'by database' loosely connects to the source parameter, but source is already described as the regional keyword database in the schema.

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 uses a specific verb ('Fetch') and a resource ('domain overview by database'), and includes the endpoint path, making the core operation clear. However, 'by database' is ambiguous and the description does not explicitly differentiate this tool from sibling tools like domainOverview or domainOverviewWorldwide.

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?

There is no guidance on when to use this tool versus alternatives such as domainOverview, domainOverviewHistory, or domainOverviewWorldwide. The description does not state any conditions, exclusions, or decision criteria, so the agent must infer usage from the endpoint and parameter names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.