Skip to main content
Glama
Sign In

Rankwise

by com.tryrankwise
OverviewDiscussionsAdmin

List AI citations

list_citations
Read-onlyIdempotent

For each tracked question and AI engine, show the latest real measurement: whether the engine cited the brand, at which position, which URLs it cited, and when. An engine that failed to answer is skipped rather than counted as not cited.

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": {
      "domain_id": "<domain_id>"
    },
    "name": "list_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return.
domain_idYesThe tracked domain's id, from list_domains.

Output Schema

NameRequiredDescriptionDefault
totalNo
domainNo
citationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 the safety profile is covered. The description adds genuine behavioral value beyond that: it discloses the edge-case rule that an engine failing to answer is skipped rather than recorded as 'not cited', and that results reflect the latest measurement rather than history.

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?

Two tight sentences with no filler; the enumeration of returned fields comes first and the non-obvious skip behavior is front-loaded in a second, separate sentence. Nothing here is wasted.

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?

An output schema exists, so the description correctly does not spend words explaining return values. For a simple 2-parameter read tool this is nearly complete; the only shortfall is the missing routing hint relative to run_citation_check and get_share_of_voice.

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?

Schema description coverage is 100%, so both domain_id and limit are already documented in the schema, including the 'from list_domains' provenance and the 1-500 bound. The description adds nothing about parameter tuning (e.g., what limit does to pagination of questions/engines), so the baseline 3 applies.

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 ('show') and resource (latest citation measurement per tracked question and AI engine) and even enumerates the returned fields: cited status, position, URLs, timestamp. It is clear what the tool does, but it never names the sibling that would trigger a fresh measurement (run_citation_check), so the boundary is inferable rather than explicit.

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?

The phrase 'latest real measurement' implies this is the read-only reporting path rather than a trigger, which is the right usage context. However, there is no explicit statement of when to call this versus run_citation_check or check_citation_readiness, and no prerequisites are given.

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

All Rankwise toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources