Skip to main content
Glama
Sign In
Semrush MCP

Semrush MCP

by mrkooblu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

semrush_keyword_overview_single_db

Read-onlyIdempotent

Retrieve detailed keyword overview data from a specific database to analyze search volume, difficulty, and trends for SEO and content strategy.

Instructions

Get detailed overview data for a keyword from 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": {
      "keyword": "<keyword>",
      "database": "<database>"
    },
    "name": "semrush_keyword_overview_single_db"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes
databaseYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/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, so the safety profile is clear. The description adds that it consumes '10 API units per line', which is a useful cost insight. However, it does not disclose return format, rate limits, or other behavioral details.

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

Conciseness3/5

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

The description is one sentence and very concise, but it omits essential details. It front-loads the purpose and cost but lacks parameter explanations and usage context, making it under-informative for its brevity.

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?

With no output schema and sparse annotations, the description should compensate but fails to explain what 'detailed overview data' includes, how to format parameters, or what the response looks like. Sibling tools like semrush_keyword_overview exist, but the description does not help differentiate.

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?

Schema coverage is 0% (no parameter descriptions), and the description provides only minimal context: it mentions 'keyword' and 'database' implicitly but does not explain accepted formats, allowed values (e.g., database codes), or the optional 'limit' parameter's meaning.

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 detailed overview data'), the resource ('a keyword'), and the scope ('from a specific database'). The name 'single_db' further distinguishes it from sibling tools like semrush_keyword_overview, though the description does not explicitly mention this distinction.

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 is provided on when to use this tool versus alternatives (e.g., semrush_keyword_overview, semrush_batch_keyword_overview). The description implies usage for single-database keyword overviews but lacks explicit context about when to prefer it.

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