Skip to main content
Glama
Sign In
Semrush MCP

Semrush MCP

by mrkooblu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

semrush_subfolder_rank_history

Read-onlyIdempotent

Retrieve historical ranking data for a specific subfolder to analyze its performance over time.

Instructions

Get historical ranking data for a subfolder

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_rank_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
subfolderYes
databaseNous
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, establishing this as a safe read operation. The description adds the adjective 'historical' but does not disclose additional behaviors such as date range limitations, pagination, or any rate limits. Since annotations carry the safety burden, a score of 3 is appropriate.

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 6-word sentence with no wasted words. However, it is arguably too concise for a tool with multiple parameters and many siblings. A slightly longer description with parameter hints would not harm 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?

Despite many sibling tools, no output schema, and 3 parameters, the description provides minimal context. It does not explain what historical ranking data includes (e.g., time range, metrics), how to interpret results, or any prerequisites. The tool feels incomplete for an AI agent to use correctly.

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?

With 0% schema description coverage, the description must compensate by explaining parameters, but it adds no information beyond parameter names and types. The agent is left guessing the meaning of 'database' (country code) and 'limit' (max results). This is a significant gap given the minimal schema.

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 verb 'Get', the resource 'historical ranking data', and the scope 'for a subfolder'. It effectively differentiates from sibling tools like semrush_subfolder_rank (current data) and semrush_subfolder_ranks (likely multiple ranks) by specifying 'historical'.

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. With many sibling tools for subfolder data (rank, ranks, organic, etc.), the agent receives no context on when historical data is appropriate or how it differs from current data. No exclusions or prerequisites are mentioned.

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