semrush-mcp

semrush_batch_keyword_overview

Analyze up to 100 keywords together in a specific regional database. Returns key SEO metrics for each keyword in one request.

Instructions

Analyze up to 100 keywords at once in a specific database (10 API units per line)

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": {
      "keywords": "<keywords>",
      "database": "<database>"
    },
    "name": "semrush_batch_keyword_overview"
  }
}

Input Schema

Name	Required	Description	Default
`keywords`	Yes	Array of keywords to analyze (max 100)
`database`	Yes	Database to use (e.g., "us", "uk", "ca", etc.)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jun 3, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so the description must carry the burden. It mentions API cost but does not disclose whether the operation is read-only, safe, or has rate limits. Critical behavioral context is missing.

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?

Single sentence that is efficient and front-loaded with the core action and constraints. No unnecessary words.

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?

The description lacks information about the return format, error handling, or how results are structured. For a batch analysis tool, this is insufficient for an agent to fully assess suitability.

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 coverage is 100% with descriptions already present. The tool description adds the API cost per line and the max 100 keywords constraint, which provides some added value, but does not significantly enhance parameter understanding beyond the schema.

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

Purpose5/5

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

The description clearly states the tool analyzes up to 100 keywords in batch within a specific database, distinguishing it from siblings like semrush_keyword_overview which handle single keywords.

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?

No guidance on when to use this batch tool versus alternatives (e.g., single keyword overviews) or how to choose a database. The description does not mention exclusions or prerequisites.

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