semrush-mcp

semrush_domain_overview

Analyze domain overview data including organic and paid search traffic, keywords, and rankings.

Instructions

Get domain overview data including organic/paid search traffic, keywords, and rankings

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": {
      "domain": "<domain>"
    },
    "name": "semrush_domain_overview"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name to analyze (e.g., "example.com")
`database`	No	Database to use (e.g., "us", "uk", "ca", etc.)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jun 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It only states what data is retrieved, but omits any discussion of side effects, rate limits, permissions, or output format. The agent cannot infer any constraints or important behavioral traits.

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 concise sentence that effectively front-loads the action ('Get domain overview data') and lists key deliverables. It is well-structured for quick comprehension, though it lacks additional useful structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple data retrieval tool with 2 parameters and no output schema, the description is minimally adequate. It tells the agent what data is included, but does not explain output format, pagination, or limitations, leaving some gaps for a fully informed call.

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?

Both parameters are fully described in the schema (domain and database). The description adds no additional meaning beyond the schema, but the high schema coverage (100%) means the baseline is 3. The description does not enhance parameter understanding further.

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 retrieves domain overview data, specifying included metrics (organic/paid traffic, keywords, rankings). While it distinguishes from more specific sibling tools by using 'overview', it does not explicitly differentiate from semrush_traffic_summary or other broad tools.

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?

No guidance is provided on when to use this tool versus sibling tools. The agent is left to infer that 'overview' implies a broad summary, but no explicit when-to-use or when-not-to-use instructions are given.

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