Skip to main content
Glama
Sign In
Semrush MCP

Semrush MCP

by mrkooblu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

semrush_subfolder_organic

Read-onlyIdempotent

Retrieve organic keywords for a domain subfolder (e.g., /blog/). Analyze keyword rankings and optimize SEO for specific site sections.

Instructions

Get organic keywords for a subfolder (e.g. domain.com/blog/)

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": {
      "subfolder": "<subfolder>"
    },
    "name": "semrush_subfolder_organic"
  }
}

Input Schema

NameRequiredDescriptionDefault
subfolderYes
databaseNous
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) sufficiently convey non-destructive, idempotent behavior. The description adds no extra behavioral context (e.g., pagination, rate limits, data scope), but the annotations already provide safety guarantees.

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 a single, clear sentence with no fluff. Every word serves a purpose. However, conciseness is not a substitute for completeness.

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 numerous sibling tools, the description lacks details on output format, pagination, and differentiation from similar tools. Requires more context for effective agent usage.

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

Parameters2/5

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

Schema coverage is 0%, meaning the description does not explain any parameter. Only the 'subfolder' parameter is hinted via example. 'database' and 'limit' are undocumented, which is insufficient for correct invocation.

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 tool retrieves organic keywords for a subfolder, with an example. It distinguishes from sibling tools like semrush_subdomain_organic by specifying 'subfolder' and 'organic', but does not explicitly differentiate from semrush_subfolder_organic_unique or paid variants.

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 alternatives (e.g., semrush_domain_organic_keywords for root domain). No mention of prerequisites or contexts where this tool is inappropriate.

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