Skip to main content
Glama
metehan777

Semrush MCP Server

by metehan777

domain_overview

Analyze domain performance by retrieving organic traffic data, keyword rankings, and authority metrics for SEO assessment.

Instructions

Get domain analytics overview including organic traffic, keywords, and authority score

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
databaseNo

Implementation Reference

  • Handler function for the 'domain_overview' tool. It parses the input arguments using DomainOverviewSchema and calls the Semrush API with the 'domain_ranks' report type, requesting specific columns like organic traffic (Or,Ot,Oc), ad traffic (Ad,At,Ac), authority score (Sh), and more.
    case 'domain_overview': {
      const { domain, database } = DomainOverviewSchema.parse(args);
      data = await callSemrushAPI('domain_ranks', {
        domain,
        database,
        export_columns: 'Db,Dn,Rk,Or,Ot,Oc,Ad,At,Ac,Sh,Sv',
      });
      break;
    }
  • Zod schema for validating inputs to the domain_overview tool: requires 'domain' string, optional 'database' string defaulting to 'us'.
    const DomainOverviewSchema = z.object({
      domain: z.string().describe('Domain to analyze'),
      database: z.string().default('us').describe('Database code (e.g., us, uk, ca)'),
    });
  • src/index.ts:174-182 (registration)
    Registration of the 'domain_overview' tool in the MCP server's listTools response, including name, description, and input schema derived from DomainOverviewSchema.
    {
      name: 'domain_overview',
      description: 'Get domain analytics overview including organic traffic, keywords, and authority score',
      inputSchema: {
        type: 'object',
        properties: DomainOverviewSchema.shape,
        required: ['domain'],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a 'Get' operation (implying read-only), but doesn't disclose any behavioral traits like authentication requirements, rate limits, data freshness, or what happens with invalid domains. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that gets straight to the point. It's appropriately sized for what it covers, though it could benefit from being more comprehensive given the tool's complexity and lack of other documentation.

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 the tool has 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain parameters, return values, or behavioral constraints. For a domain analytics tool that likely returns complex data, this leaves too many unknowns for effective use.

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

Parameters2/5

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

With 0% schema description coverage for 2 parameters, the description provides no information about parameters. It doesn't mention the 'domain' or 'database' parameters at all, nor does it explain what values are expected (e.g., format for domain, valid database codes). The description fails to compensate for the complete lack of schema documentation.

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') and the resource ('domain analytics overview') with specific metrics mentioned (organic traffic, keywords, authority score). It distinguishes from some siblings like 'backlinks_overview' or 'keyword_overview' by focusing on comprehensive domain analytics rather than specific aspects, though it doesn't explicitly differentiate from all alternatives.

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?

The description provides no guidance on when to use this tool versus its siblings. With tools like 'domain_organic_search' and 'keyword_overview' available, there's no indication of when this comprehensive overview is preferred over more specific tools or what scenarios warrant its use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/metehan777/semrush-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server