Skip to main content
Glama

List changes

list_changes
Read-onlyIdempotent

The change feed: every settled run, every poll made public or private, every new version and every revision of published answers, oldest first, after a cursor. Needs a free key with read: public polls' changes by default, and mine=true for your own polls'. Keep next_cursor and ask again later, adding a random minute so every client does not ask at once; or register a webhook to be told. (GET /api/v1/changes)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
mineNotrue: your own polls' changes (needs a key with read). Default: public polls'.
limitNoEvents per page, 1 to 500.
typesNoComma-separated event types to include. Default: all.
cursorNonext_cursor from the previous page. Leave it out to start from the oldest kept event.
poll_idNoOnly this poll's changes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description still adds real value beyond them: the read-scope auth requirement, that public polls are the default surface, and the cursor/jitter polling etiquette. It stops short of describing the event payload shape, which keeps it at a middling score rather than high.

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?

It front-loads what the feed contains, then auth, then pagination, then the webhook alternative, with zero filler sentences. The prose is dense and slightly run-on across clauses, but every clause carries information an agent needs.

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 five optional params, no output schema, and modest complexity, the definition covers what the caller must know: auth scope, default filtering, ordering, cursor continuation, and rate-friendliness. The only gap is that it does not sketch the event record fields a caller receives, which matters slightly more because there is no output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds practical meaning for two parameters: how to use next_cursor ('keep next_cursor and ask again later') and what mine=true selects. The random-minute jitter advice is behavioral context the schema cannot express.

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?

The description names the resource precisely ('the change feed') and enumerates its contents: settled runs, poll visibility changes, new versions, and answer revisions, ordered oldest first from a cursor. That is far more specific than the bare title and lets an agent distinguish it from list_runs or list_polls, though it never explicitly contrasts itself with those siblings.

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

Usage Guidelines4/5

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

It states prerequisites (free key with read scope), the default scope (public polls only) versus mine=true for your own, and an alternative path ('register a webhook to be told'). What it lacks is an explicit when-not-to-use-this-poller-in-favor-of-a-list-endpoint rule, but the polling-vs-webhook choice is actionable.

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.