Skip to main content
Glama

Semrush

by io.github.pipeworx-io

Domain Organic Keywords

domain_organic_keywords
Read-onlyIdempotent

Top organic search keywords a domain ranks for (Semrush type=domain_organic). Returns parsed rows with columns: Ph (keyword phrase), Po (current position), Pp (previous position), Nq (search volume), Cp (CPC), Ur (ranking URL), Tr (traffic %), Co (competition), Nr (number of results). Consumes your Semrush API units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to analyze, e.g. "apple.com".
_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.
display_sortNoSort order, e.g. "tr_desc" (traffic), "nq_desc" (volume), "po_asc" (position). Optional.
display_limitNoMax keywords to return (default Semrush 10000; pass a small value like 50).

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is clear. The description adds value by disclosing that the tool consumes Semrush API units, which is a key behavioral cost. No contradictions with annotations.

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 extremely concise: two sentences that front-load the core purpose and return format, followed by a critical behavioral note. Every word earns its place with no fluff.

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 5-parameter tool with no output schema, the description provides the column list and API unit consumption. It does not explain pagination or default limits, but these are available in the schema. Overall, it is sufficiently complete for common use.

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 description coverage is 100%, with clear descriptions for all 5 parameters in the input schema. The description does not add significant new meaning beyond the schema, maintaining the baseline score.

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's purpose: retrieving top organic search keywords for a domain, sourced from Semrush. It specifies the resource (domain), action (keywords), and data source, distinguishing it from paid keyword or keyword overview tools.

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?

The description mentions that using the tool consumes Semrush API units but does not explicitly state when to use this tool versus alternatives. The sibling tool names hint at differentiation (e.g., domain_paid_keywords), but the description lacks direct usage guidance or exclusion criteria.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap: ask_pipeworx and ask_pipeworx_grounded are very similar, and the multiple Polymarket tools could be confused. The memory tools (remember, recall, forget) are distinct.

Naming Consistency3/5

Tool names consistently use snake_case, but the pattern is not strictly verb_noun. Some names are descriptive phrases (e.g., scan_competitor_ai_presence), while others are straightforward (e.g., keyword_overview). Overall readable but not highly consistent.

Tool Count3/5

32 tools is on the high side for a single server, but the scope is broad (SEO, finance, FDA, betting, memory). The tool count feels slightly excessive, yet each tool appears justified by its specific use case.

Completeness4/5

The tool set covers a wide range of business research needs: SEO, SEC filings, FDA data, betting analytics, and memory. Minor gaps exist (e.g., no direct social media or HR data), but the coverage is impressive for a general-purpose data server.

Resources