Skip to main content
Glama

Rankings: where a client ranks today

rank_report
Read-onlyIdempotent

Where a client ranks today for the terms rank_track follows: Search Console position against a week and a month ago, clicks and impressions, and the map-pack position from the last Monday check. Read-only.

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": {
      "client": "<client>"
    },
    "name": "rank_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYesClient name from list_clients

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so 'Read-only' in the description is redundant and earns no credit. What does add value is the disclosure of data provenance and freshness: Search Console positions compared against a week and a month ago, clicks/impressions, and the map-pack position taken from the last Monday check. That freshness constraint is real behavioral context an agent cannot get from the schema or 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?

A single front-loaded sentence that leads with the core purpose and then itemizes the returned metrics; every clause carries information. The colon list is dense but not padded, though it reads as one long run-on rather than cleanly separated statements.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly compensates by describing what the report contains (positions vs. week/month, clicks, impressions, map-pack). It is complete enough for an agent to know what a call returns and that it requires a client with tracked terms, missing only minor details like historical depth or empty-state behavior.

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

Parameters3/5

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

Single parameter with 100% schema description coverage ('Client name from list_clients'), so the schema already carries the meaning. The description only indirectly adds parameter context through 'the terms rank_track follows', but does not explain the client identifier format or validation beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: it reports where a client currently ranks for the terms rank_track follows, and enumerates the data included (GSC position vs. week/month, clicks, impressions, map-pack). This clearly separates it from rank_track (which sets up the tracked terms) and from generic tools like gsc_query. It never explicitly names a sibling alternative, so it lands just short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer 'use this to read current rankings for a client', and the reference to 'terms rank_track follows' presupposes a prior rank_track setup. But there is no explicit when/when-not guidance and no pointer to alternative ranking or search-console tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.