Skip to main content
Glama

Canon Episode Search

canon_episode_search
Read-onlyIdempotent

Search the CanonCannon episode corpus, 10,000+ podcast episodes with the ideas, guests and books extracted from each. Filter by show, by publication date, or by free text. Requires a CanonCannon API key via _apiKey. Example: canon_episode_search({ query: "sleep apnea", since: "2026-01-01" }).

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": {
      "query": "sleep apnea",
      "since": "2026-01-01"
    },
    "name": "canon_episode_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEpisodes per page, 1-100. Default 25.
queryNoFree-text search over episode titles and extracted content.
sinceNoOnly episodes published on or after this date, YYYY-MM-DD.
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
podcastNoCanonCannon podcast slug, from canon_podcast_list.

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered upstream. The description adds corpus size and the fact that extracted ideas/guests/books are searchable, plus the API-key prerequisite, but says nothing about rate limits, result ordering, or how deep pagination behaves.

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?

Three tight sentences plus one inline example, with the corpus description and filter options front-loaded. The API-key sentence partially duplicates the _apiKey schema description, which is the only real redundancy.

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?

For a read-only search tool with no output schema, the definition covers what is searched, how it can be filtered, and the auth requirement adequately. A short note on what a result record contains (or that the response carries next_cursor) would close the remaining gap.

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 the schema already explains query, since, limit, cursor, podcast and _apiKey in detail; the baseline is therefore 3. The description only restates the filter axes (show, date, free text) and repeats the API-key requirement already spelled out in the _apiKey schema entry, adding no format or syntax detail beyond the concrete example call.

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?

Names a specific verb and resource ("Search the CanonCannon episode corpus") and quantifies scope with "10,000+ podcast episodes with the ideas, guests and books extracted from each," which tells an agent exactly what content is indexed. It does not explicitly differentiate from the sibling canon_search, so an agent must infer that the episode corpus here is podcast-specific rather than general.

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?

"Filter by show, by publication date, or by free text" communicates the available selection strategies, and the worked example shows a realistic combined query. There is no when-not guidance, no mention of when to prefer canon_search or canon_episode_get, and no stated relationship to the other CanonCannon retrieval 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.