Skip to main content
Glama
metehan777

Semrush MCP Server

by metehan777

related_keywords

Discover keyword variations and suggestions to expand SEO research based on a seed phrase.

Instructions

Get related keywords and suggestions for a seed keyword

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phraseYes
databaseNo
limitNo

Implementation Reference

  • The handler logic for 'related_keywords' tool: parses input arguments using the schema, calls Semrush API with 'phrase_related' report type and specific parameters/export_columns, and assigns the result to 'data' for further processing.
    case 'related_keywords': {
      const { phrase, database, limit } = RelatedKeywordsSchema.parse(args);
      data = await callSemrushAPI('phrase_related', {
        phrase,
        database,
        display_limit: limit,
        export_columns: 'Ph,Nq,Cp,Co,Nr,Td,Rr',
      });
      break;
    }
  • Zod schema defining the input parameters for the 'related_keywords' tool: phrase (required string), database (optional string, default 'us'), limit (optional number, default 10).
    const RelatedKeywordsSchema = z.object({
      phrase: z.string().describe('Seed keyword phrase'),
      database: z.string().default('us').describe('Database code'),
      limit: z.coerce.number().default(10).describe('Number of results'),
    });
  • src/index.ts:228-236 (registration)
    Tool registration in the list of available tools: specifies name 'related_keywords', description, and inputSchema based on RelatedKeywordsSchema.
    {
      name: 'related_keywords',
      description: 'Get related keywords and suggestions for a seed keyword',
      inputSchema: {
        type: 'object',
        properties: RelatedKeywordsSchema.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 full burden for behavioral disclosure. It states 'Get' which implies a read operation, but doesn't describe response format, rate limits, authentication needs, or potential side effects. For a tool with 3 parameters and no annotation coverage, this is insufficient.

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 states the core purpose without unnecessary words. It's appropriately sized for a simple tool and front-loads the essential information.

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?

For a tool with 3 parameters, 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'related keywords and suggestions' means in practice, how results are returned, or provide context about the 'database' parameter which appears to be a key input.

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 all 3 parameters are undocumented in the schema. The description mentions only 'seed keyword' which maps to the 'phrase' parameter, leaving 'database' and 'limit' completely unexplained. The description fails to compensate for the schema's lack of 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 verb ('Get') and resource ('related keywords and suggestions') with the target ('for a seed keyword'). It distinguishes from siblings like 'keyword_overview' by focusing on related terms rather than keyword metrics. However, it doesn't explicitly differentiate from all siblings, keeping it from a perfect score.

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 'keyword_overview' or 'competitor_research'. It lacks context about appropriate use cases, prerequisites, or exclusions, leaving the agent with minimal usage direction.

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