semrush_domain_rankAnalyze a domain's organic and paid search visibility in a chosen regional database to assess search performance.
Overview of a domain's organic and paid search visibility in one regional database.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | ||
| database | No | Regional database code, e.g. us, uk, de, fr, es, it, br, au, ca, in (default: us) | us |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not state whether the operation is read-only, what permissions are needed, whether data is live or cached, or what the return structure looks like, leaving key behavioral traits undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the tool's scope.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations and no output schema, the description is too thin. It does not explain the domain input format, what metrics or rankings are returned, or how it differs operationally from semrush_domain_overview, leaving an agent underprepared to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%: the database parameter has a description, but the required domain parameter has none. The description mentions 'one regional database' but adds no format details for domain or database beyond what the schema already states, so it fails to compensate for the undocumented domain parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies the resource (a domain's organic and paid search visibility) and scopes it to one regional database, which distinguishes it from multi-database or history siblings. It is clear but does not explicitly name the sibling tool it is not, so an agent must infer the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool versus semrush_domain_overview, semrush_domain_rank_history, or other siblings. The phrase 'one regional database' hints at a condition but does not state when that condition applies or what alternatives exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.