Skip to main content
Glama
Sign In
Semrush MCP

Semrush MCP

by mrkooblu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

semrush_traffic_summary

Read-onlyIdempotent

Retrieve traffic summary data for domains to analyze website traffic volume and trends using Semrush Trends API.

Instructions

Get traffic summary data for domains (requires .Trends API access)

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": {
      "domains": "<domains>"
    },
    "name": "semrush_traffic_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYes
countryNous

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which provide safety information. The description adds the requirement for '.Trends API access', a behavioral constraint. However, it does not disclose other behavioral traits like rate limits, response size, or whether the tool handles large domain lists efficiently.

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

Conciseness5/5

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

A single, front-loaded sentence with no filler. Every word is purposeful: 'Get traffic summary data for domains' states the operation, and '(requires .Trends API access)' adds a critical constraint. Ideal length for quick scanning.

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 explain what 'traffic summary data' includes (e.g., metrics like visits, page views, etc.). It does not. With two parameters and one required, the description is minimal and incomplete for an agent to fully understand the tool's results. Annotations help with safety but not completeness.

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%, meaning no parameter descriptions in the schema. The tool description fails to explain what 'domains' or 'country' mean, nor does it provide format details or examples. For instance, 'country' defaults to 'us' but is not clarified. The description adds no value beyond the schema structure.

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 verb 'Get' and resource 'traffic summary data for domains', indicating a read operation. However, it does not differentiate from sibling tools like semrush_traffic_accuracy or semrush_traffic_destinations, which also deal with traffic data. The mention of '.Trends API access' adds specificity but doesn't clarify what 'summary' entails vs other traffic 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?

There is no guidance on when to use this tool versus alternatives such as semrush_traffic_sources or semrush_traffic_subdomains. The description lacks context about usage scenarios, prerequisites (beyond API access), or exclusions, leaving the agent to infer appropriateness.

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

Deploy Server

Other Tools