AIsa SEO & AI Visibility

Semrush Domain Overview

get_semrush_domain_overview

Read-onlyIdempotent

Published reference price: $0.001 USD per successful request. Account-specific pricing and final settlement may differ.

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": "get_semrush_domain_overview"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes
`database`	No		us

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

removedInput schema / properties / database / description

Removed value: -"Regional database / country code. Defaults to `us`. Examples: `us`, `uk`, `cn`."

removedInput schema / properties / domain / description
```
Removed value: -"Target domain, e.g. `ahrefs.com`."
```

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / database / description

Added value: +"Regional database / country code. Defaults to `us`. Examples: `us`, `uk`, `cn`."

addedInput schema / properties / domain / description
```
Added value: +"Target domain, e.g. `ahrefs.com`."
```

Changed2 schema fields changedOct 15, 2026

removedInput schema / properties / database / description

Removed value: -"Regional database / country code. Defaults to `us`. Examples: `us`, `uk`, `cn`."

removedInput schema / properties / domain / description
```
Removed value: -"Target domain, e.g. `ahrefs.com`."
```

First observedSep 15, 2026

TDQS

D1.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description does add one genuine behavioral fact not in the annotations – a per-request price of $0.001 USD – which is useful cost context, but it discloses nothing about auth requirements, rate limits, or response behavior.

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

Conciseness2/5

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

It is short, but the content is boilerplate HTML-comment pricing markup that does not help an agent select or invoke the tool. Length is minimal while relevance is near zero, so it is under-specified rather than concise.

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

Completeness1/5

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

For a domain-overview tool with a required 'domain' parameter and an undocumented 'database' parameter, the description leaves the agent without the essential information needed to call it correctly. The presence of an output schema excuses explaining return values, but nothing else compensates for the missing purpose and parameter detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters ('domain' and 'database'), and the description supplies no meaning, format, or defaults for either. It does not compensate for the schema gap at all, and notably omits that 'database' defaults to 'us'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what the tool does; it contains only a pricing notice wrapped in HTML comments. An agent must infer the purpose entirely from the tool name 'get_semrush_domain_overview'. It provides no verb+resource statement and no differentiation from siblings like get_semrush_domain_organic_keywords or get_semrush_domain_vs_domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of alternatives among the many semrush/ahrefs/dataforseo siblings. The text is solely about cost, not about selection.

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

All AIsa SEO & AI Visibility tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?