Semrush Keyword Magic Tool MCP Server

keyword_overview_analysis

Get keyword overview data like search volume, difficulty, and CPC for a target keyword in any country to guide SEO decisions.

Instructions

Keyword Overview analysis

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": {
      "keyword": "<keyword>",
      "country": "<country>"
    },
    "name": "keyword_overview_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`country`	Yes	Example value: us
`keyword`	Yes	Example value: ai tools

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 7, 2026

TDQS

D1.9/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of explaining behavioral traits. It merely states 'analysis' with no details on whether it is read-only, what side effects exist, what the output format is, or any constraints. This is even less informative than typical mutation descriptions.

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?

The description is extremely short, but this is under-specification, not effective conciseness. It does not include essential structural elements like purpose, expected input semantics, or output behavior, making it insufficient for an agent to use correctly.

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?

Given the tool has only two params and no output schema or annotations, the description still fails to provide minimal context. It does not explain what kind of analysis is performed, what the result looks like, or how it relates to sibling tools, leaving the agent completely uninformed.

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?

Schema description coverage is 100%, so the baseline is 3. The description itself adds no extra meaning beyond the schema, but the example values in the schema provide some format guidance. The description does not enhance the semantic understanding of 'keyword' or 'country' beyond what is already present.

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

Purpose2/5

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

The description 'Keyword Overview analysis' essentially restates the tool name without a specific verb or resource. It does not distinguish from sibling tools like keyword_magic_tool or questions, and it lacks actionable clarity about what the tool actually does.

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 alternatives. It does not mention any context, prerequisites, or exclusions, leaving the agent without direction for tool selection.

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

Deploy Server