Skip to main content
Glama

Semrush

by io.github.pipeworx-io

Domain Paid Keywords

domain_paid_keywords
Read-onlyIdempotent

Paid (AdWords/PPC) keywords a domain bids on (Semrush type=domain_adwords). Returns parsed rows with columns: Ph (keyword phrase), Po (ad position), Nq (search volume), Cp (CPC), Ur (landing page URL), Tg (traffic), Tc (traffic cost), 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_limitNoMax keywords to return (pass a small value like 50).

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already signal read-only, idempotent, non-destructive behavior. Description adds that it consumes Semrush API units and details the return format (columns), providing useful context beyond annotations.

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

Conciseness4/5

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

Description is compact but packs essential information. Could be slightly better structured (e.g., bullet list for columns), but every sentence adds value.

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

Completeness5/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 return columns, explains API cost, and covers all 4 parameters. Sufficient for an agent to decide and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds meaning for each parameter: notes that _apiKey is BYO and consumes units, gives domain example, explains database as 2-letter regional code with default, and suggests small value for display_limit.

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 it returns paid keywords (AdWords/PPC) for a domain via Semrush, specifying the type parameter and output columns. Distinguishes itself from domain_organic_keywords by explicitly mentioning paid nature.

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

Usage Guidelines4/5

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

Describes when to use (to get paid keywords), but doesn't explicitly say when not to use or list alternatives. However, sibling list includes domain_organic_keywords, providing implicit differentiation.

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