semrush-mcp

semrush_competitors

Identify organic search competitors for any domain. Analyze competing websites to refine your SEO strategy.

Instructions

Get competitors for a specific domain in organic search

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_competitors"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	Domain name to analyze (e.g., "example.com")
`database`	No	Database to use (e.g., "us", "uk", "ca", etc.)
`limit`	No	Maximum number of competitors to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jun 3, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Without annotations, the description should disclose behavioral traits such as rate limits, data freshness, or the definition of 'competitors'. The current description provides none of these, offering only the bare minimum one-line statement.

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 sentence, which is concise but arguably too terse. It does not waste words, but could be expanded to include key details without becoming verbose.

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 no output schema, the description should indicate what the tool returns (e.g., list of competitor domains, metrics). It also does not specify the scope of 'organic search' or any limitations. The description is insufficient for full understanding.

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?

All three parameters are described in the schema with 100% coverage. The description adds no additional meaning beyond the schema, e.g., by explaining optional interplay or formatting constraints. Baseline score of 3 is appropriate.

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 action ('Get competitors') and the target resource ('domain in organic search'). It effectively distinguishes this tool from siblings like 'semrush_domain_organic_keywords' which focuses on keywords rather than competitors.

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 information is provided about when to use this tool versus alternative Semrush tools (e.g., 'semrush_domain_overview' or 'semrush_backlinks'). The description lacks context on prerequisites or scenarios that favor this tool.

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