Skip to main content
Glama
Sign In
Semrush MCP

Semrush MCP

by mrkooblu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

semrush_subdomain_organic

Read-onlyIdempotent

Retrieve organic keywords ranking for a subdomain to analyze its search performance and identify optimization opportunities.

Instructions

Get organic keywords for a subdomain

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": {
      "subdomain": "<subdomain>"
    },
    "name": "semrush_subdomain_organic"
  }
}

Input Schema

NameRequiredDescriptionDefault
subdomainYes
databaseNous
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no additional behavioral context (e.g., rate limits, data freshness). It is consistent but not informative beyond 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.

Conciseness4/5

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

The description is a single, concise sentence with no wordiness. However, it is too brief and lacks necessary details, which reduces the value of its conciseness.

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 tool has 3 parameters, no output schema, and no param descriptions, the one-sentence description is insufficient. It does not cover what the tool returns, any constraints, or expected behavior.

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?

Schema has 3 parameters with 0% description coverage. The description does not explain any parameter meanings, such as what subdomain format is expected, what database values are valid, or how limit behaves.

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 'Get organic keywords for a subdomain' clearly states the verb and resource. It distinguishes from sibling tools like semrush_domain_organic_keywords and semrush_subfolder_organic by specifying 'subdomain', though it does not explicitly contrast with them.

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 guidance on when to use this tool versus siblings (e.g., semrush_domain_organic_keywords). No conditions, prerequisites, or context provided.

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