Skip to main content
Glama

Semrush

by io.github.pipeworx-io

Organic Competitors

organic_competitors
Read-onlyIdempotent

Organic search competitors for a domain (Semrush type=domain_organic_organic). Returns parsed rows with columns: Dn (competitor domain), Cr (competition level), Np (common keywords), Or (competitor organic keywords), Ot (competitor organic traffic), Oc (organic cost). Consumes your Semrush API units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to find competitors for, 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_limitNoMax competitors to return (pass a small value like 25).

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. The description adds that it consumes Semrush API units and details the returned columns (Dn, Cr, etc.), which informs about output structure. No contradictions.

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?

Two sentences, clear and front-loaded: first sentence states purpose and output, second adds cost context. No unnecessary words.

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?

No output schema, but description lists all returned columns and their meanings. Also explains the API type and cost. Adequate for a data retrieval tool with well-annotated schema.

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 4 parameters with descriptions. The description does not add new semantic information about parameters beyond the schema, but the baseline is 3 due to high schema coverage.

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 finds organic search competitors for a domain, specifies the Semrush API type, and lists the output columns. It is distinct from sibling tools like domain_organic_keywords or domain_overview.

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 explicit guidance on when to use this tool versus alternatives like domain_organic_keywords or backlinks_overview. Only mentions API unit consumption, which is a cost note, not usage 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