Skip to main content
Glama

List weekly keyword rank reports

list_keyword_rank_reports
Read-onlyIdempotent

Weekly keyword rank reports for an application, newest first: rank change of each baselined term since the variant was applied, new top-10 terms, terms no longer ranked, and the applied draft's modeled coverage. Read-only; spends nothing.

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": {
      "application_id": "<application_id>"
    },
    "name": "list_keyword_rank_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesApplication id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, non-destructive, idempotent and closed-world, so 'Read-only' largely repeats structured data. The genuinely additive detail is cost: 'spends nothing' tells the agent no credits are consumed, and 'newest first' discloses ordering, but nothing is said about pagination, limits, or empty-state behavior.

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 dense sentence that front-loads the resource and then lists returned fields, followed by a short qualifier. No filler, though the colon-separated field list is packed enough to need a second read.

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?

No output schema exists, and the description compensates by enumerating what the report contains and the sort order. For a one-parameter, read-only listing tool with rich annotations, only details like result-set size or pagination are missing.

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?

Only one parameter (application_id) with 100% schema description coverage, so the schema already carries the burden. The description adds no meaning beyond it—no note on format, scoping, or what happens with an unknown id—which is the expected baseline for a single fully-documented parameter.

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?

Specific resource (weekly keyword rank reports) plus a precise enumeration of contents: rank change of baselined terms, new top-10 terms, dropped terms, and modeled coverage of the applied draft. It is clearly a listing tool, though it never names the sibling that returns per-term history (get_keyword_rank_history) to sharpen the boundary.

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 only implied: 'weekly ... newest first' suggests this is the periodic summary view, and 'read-only; spends nothing' hints it is safe to call freely. There is no explicit when-to-use or when-not-to-use statement versus alternative keyword rank 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.

Resources