Skip to main content
Glama
Sign In
Semrush MCP

Semrush MCP

by mrkooblu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

semrush_domain_shopping

Read-onlyIdempotent

Retrieve Product Listing Ads (PLA) search keywords for a given domain to analyze competitors' shopping ad strategies.

Instructions

Get PLA (Product Listing Ads) search keywords for a domain

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": {
      "domain": "<domain>"
    },
    "name": "semrush_domain_shopping"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
databaseNous
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

The description only repeats the action 'Get', which is already implied by the readOnlyHint annotation. No additional behavioral traits are disclosed, such as data freshness, rate limits, or potential side effects beyond what annotations already state.

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?

The description is a single sentence of 10 words, achieving high conciseness. It front-loads the core purpose. However, it could include slightly more detail without becoming verbose.

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?

Given the lack of output schema and only minimal parameter information from the schema, the description fails to provide sufficient context about the return value format, the meaning of 'database' and 'limit', or any other operational details needed for correct usage.

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

Parameters1/5

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

The input schema has zero description coverage for its three parameters (domain, database, limit), and the tool description does not explain their meaning or usage. This leaves the agent to infer entirely from parameter names, which may be ambiguous (e.g., 'database' likely refers to a country code but is not clarified).

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 verb 'Get' and the resource 'PLA (Product Listing Ads) search keywords for a domain', making the purpose specific and understandable. However, it does not differentiate from the sibling tool semrush_domain_shopping_unique, which likely has a similar purpose.

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 is provided on when to use this tool versus alternatives, such as semrush_domain_shopping_unique or other keyword-related tools. The description lacks any context about prerequisites or exclusions.

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