Skip to main content
Glama
metehan777

Semrush MCP Server

by metehan777

keyword_overview

Analyze keyword metrics like search volume, difficulty, and CPC to inform SEO strategy and content planning.

Instructions

Get keyword metrics including search volume, difficulty, and CPC

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phraseYes
databaseNo

Implementation Reference

  • The handler logic for the 'keyword_overview' tool. It parses the input arguments using KeywordOverviewSchema and calls the Semrush API with the 'phrase_all' report type to retrieve keyword metrics.
    case 'keyword_overview': {
      const { phrase, database } = KeywordOverviewSchema.parse(args);
      data = await callSemrushAPI('phrase_all', {
        phrase,
        database,
        export_columns: 'Ph,Nq,Cp,Co,Nr,Td',
      });
      break;
    }
  • Zod schema defining the input parameters for the keyword_overview tool: 'phrase' (required string) and 'database' (optional string, defaults to 'us').
    const KeywordOverviewSchema = z.object({
      phrase: z.string().describe('Keyword phrase to analyze'),
      database: z.string().default('us').describe('Database code'),
    });
  • src/index.ts:183-191 (registration)
    Registration of the 'keyword_overview' tool in the MCP server's tool list, specifying name, description, and input schema derived from KeywordOverviewSchema.
    {
      name: 'keyword_overview',
      description: 'Get keyword metrics including search volume, difficulty, and CPC',
      inputSchema: {
        type: 'object',
        properties: KeywordOverviewSchema.shape,
        required: ['phrase'],
      },
    },
Behavior2/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 behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't mention any side effects, rate limits, authentication requirements, or error conditions. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and immediately lists the key metrics, making it easy to understand at a glance.

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 insufficient. It doesn't explain parameter usage, return values, or behavioral traits. For a keyword analysis tool that likely returns structured data, more context is needed to use it effectively.

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?

The schema description coverage is 0%, meaning neither parameter has descriptions in the schema. The tool description mentions 'keyword metrics' but doesn't explain what the 'phrase' or 'database' parameters mean, their expected formats, or how they affect the analysis. With 2 parameters and no schema documentation, the description fails to compensate for this gap.

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 ('keyword metrics') with specific metrics listed (search volume, difficulty, CPC). It distinguishes this tool from siblings like 'backlinks_overview' or 'domain_overview' by focusing on keyword analysis rather than backlinks or domains. However, it doesn't explicitly contrast with 'related_keywords' which might also involve keyword data.

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 like 'related_keywords' or 'competitor_research'. It mentions what metrics are retrieved but offers no context about appropriate use cases, prerequisites, or limitations compared to sibling tools.

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