Skip to main content
Glama

List a poll's runs

list_runs
Read-onlyIdempotent

A poll's runs, newest first: when each was due, started and finished, its status and counts, and available_at, when this reader could first have read it. A stranger sees only runs that have become available; the owner also sees queued and running ones, and charges. (GET /api/v1/polls/{id}/runs)

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": {
      "id": "<id>"
    },
    "name": "list_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe poll's id, or its public address (slug).
limitNoItems per page, 1 to 100.
cursorNonext_cursor from the previous page, unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior: results are ordered newest-first, and the visible set depends on identity — anonymous callers see only runs that have become available, while the owner also sees queued/running runs and charges. That permission-dependent result set is exactly the kind of context annotations cannot express. It stops short of telling the reader anything about pagination exhaustion or empty-result 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?

Two compact sentences, front-loaded with the resource and its ordering before the visibility caveat. It is dense but not wasteful; the trailing 'GET /api/v1/polls/{id}/runs' is redundant for an agent that never makes raw HTTP calls and could be dropped.

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?

There is no output schema, so the description shoulders the burden of describing the return shape, and it does so field by field. With all three params documented in-schema and read-only annotations present, the only real omission is guidance on iterating pages via cursor, which the schema mostly covers.

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%, with id, limit and cursor each documented in-schema, so the baseline is 3. The description adds nothing about parameter formats or defaults; its only semantic contribution ('available_at, when this reader could first have read it') explains a returned field, not an input.

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 states a concrete resource ('A poll's runs') and enumerates its shape: due/start/finish timestamps, status, counts, and available_at, returned newest first. That is far more specific than the title alone, though it never contrasts itself with nearby siblings such as get_live_run or get_results, so an agent must infer 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: you call this to see a poll's run history. There is no explicit 'use this when...' statement and no named alternative for the case where the agent wants results rather than run metadata. The visibility note (stranger vs owner) is about what comes back, not about when to pick this tool over another.

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.