Skip to main content
Glama

List Rank Tracker scans

list_rank_scans
Read-onlyIdempotent

List Rank Tracker grid scans for a profile (keyword, grid size, date) with average and top-3 share summaries.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "list_rank_scans"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordNo
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description does add value by disclosing that each row carries average and top-3 share summaries (useful given there is no output schema), but it says nothing about ordering, pagination, or how the limit is applied.

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?

A single front-loaded sentence with no filler; scope, filter dimensions, and returned summaries are all packed into it without redundancy.

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

Completeness3/5

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

For a read-only list tool with three parameters, zero schema documentation and no output schema, the description covers intent and return shape but leaves the limit/pagination contract and result ordering unexplained. Adequate to attempt a call, not complete enough to call confidently with non-default paging.

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 description coverage is 0%, so the description must carry parameter meaning, but it never mentions the `limit` parameter at all. The parenthetical "(keyword, grid size, date)" plausibly describes scan attributes rather than inputs, since no grid-size or date parameter exists, which risks misleading the agent about what it can filter on.

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?

Names a specific verb+resource ("List Rank Tracker grid scans") and scopes it to a profile with the dimensions carried (keyword, grid size, date) plus the summary metrics returned. It does not explicitly distinguish itself from the sibling get_rank_scan (single scan) or list_citation_scans, so sibling differentiation is only implicit.

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?

There is no guidance on when to use this versus get_rank_scan for a single scan or request_rank_scan to kick off a new one, and no prerequisites or exclusions are stated. The only hint is that listing is per-profile, which the required profile_id already conveys.

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.

Resources