Skip to main content
Glama
Sign In

Semrush

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Keyword Overview

keyword_overview
Read-onlyIdempotent

Keyword overview (Semrush type=phrase_this): search metrics for a single keyword phrase. Returns parsed rows with columns: Ph (phrase), Nq (search volume), Cp (CPC), Co (competition 0-1), Nr (number of organic results), Td (trend, last 12 months as |-separated values). Consumes your Semrush API units.

Input Schema

NameRequiredDescriptionDefault
phraseYesKeyword phrase to look up, e.g. "running shoes".
_apiKeyYesYour own Semrush API key (BYO). Passed to Semrush as the `key` query param. Consumes your Semrush API units.
databaseNo2-letter Semrush regional database (e.g. us, uk, de, fr, es, ca, au). Default us.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-semrush-api-key",
+    "phrase": "running shoes"
+  },
+  {
+    "_apiKey": "your-semrush-api-key",
+    "database": "us",
+    "phrase": "best laptops 2024"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnly, idempotent, openWorld. Description adds important cost info 'Consumes your Semrush API units' and details returned columns, exceeding what annotations provide.

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?

Three sentences, no verbosity: purpose, return format, cost. Front-loaded and every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with 3 params and no output schema, description explains purpose, columns, and cost. Could optionally include an example value, but complete enough.

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 covers all 3 parameters with descriptions (100% coverage). Description adds no extra meaning beyond schema, so baseline 3 is appropriate.

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?

Description clearly states the verb 'search metrics' and resource 'single keyword phrase', and distinguishes from sibling tools like domain_overview which focus on domains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage for single keyword phrase, but no explicit when-to-use or when-not-to-use compared to alternatives like domain_organic_keywords.

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

All Semrush toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources