Skip to main content
Glama

Canon Podcast List

canon_podcast_list
Read-onlyIdempotent

Every podcast CanonCannon tracks, with its episode count, the roster that forms the denominator of the canon bar (an idea needs ceil(5%) of these shows to clear it). Requires a CanonCannon API key via _apiKey. Example: canon_podcast_list({ limit: 100 }).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPodcasts per page, 1-100. Default 50.
cursorNoKeyset cursor from a previous call's next_cursor.
_apiKeyNoCanonCannon API key (cc_live_...). Every /api/v1 endpoint refuses without it. Keys are issued by CanonCannon, https://canoncannon.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"CanonCannon API key (cc_live_...). Every /api/v1 endpoint refuses without it. Keys are issued by CanonCannon — https://canoncannon.com"New value: +"CanonCannon API key (cc_live_...). Every /api/v1 endpoint refuses without it. Keys are issued by CanonCannon, https://canoncannon.com"
  2. 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 readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds context the annotations cannot: the auth requirement ('Requires a CanonCannon API key via _apiKey') and the domain meaning of the returned roster as the denominator of the canon bar. It does not spell out pagination behavior despite exposing a cursor.

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 dense sentences plus an example, front-loaded with the resource and scope. The parenthetical defining the canon bar is slightly nested but earns its place by explaining the roster's significance; nothing is padding.

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

Completeness5/5

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

For a simple read-only listing tool with full schema coverage and rich annotations, the definition supplies everything needed: scope, required auth, the meaning of the payload, and a call example. No output schema exists, but the description already characterizes what comes back (podcasts with episode counts).

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 coverage is 100%, so limit, cursor and _apiKey are already documented in the schema. The description only reinforces the _apiKey requirement and supplies a sample call with limit: 100; it adds no new meaning about cursor semantics or default paging beyond the schema.

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?

Opens with a specific verb and resource -- every podcast CanonCannon tracks -- and adds what each record carries (episode count, roster). It is clearly distinguishable from canon_podcast_get by its 'every podcast' scope, though it never names the sibling to make the contrast 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?

Usage is implied by 'every podcast CanonCannon tracks' rather than stated: an agent can infer this is the enumeration call versus a single-podcast lookup. There is no explicit when-to-use, no mention of canon_podcast_get, and no guidance on when pagination (cursor) should be followed.

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.