Skip to main content
Glama

Get a Yedapo episode summary

get_episode
Read-onlyIdempotent

Get one episode's full Yedapo summary as markdown: teaser, should-you-listen verdict, key takeaways with timestamps, a short verbatim source snippet with a timestamp when a transcript is available, chapter breakdown, and the page URL to cite. Newest summary added: 2026-11-18.

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": {
      "episode": "<episode>"
    },
    "name": "get_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
episodeYesEpisode UUID, or any yedapo.com episode URL (the UUID is extracted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond them: the conditional 'when a transcript is available' caveat on the verbatim snippet, and a freshness signal ('Newest summary added: 2026-11-18') telling the agent how current the corpus is.

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?

A single dense sentence, front-loaded with the action and return format, followed by the field breakdown and one caveat. Every clause carries information; nothing is redundant.

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?

There is no output schema, and the description compensates by enumerating the returned sections and noting the conditional transcript snippet and the citable page URL. Combined with full schema coverage on the single parameter, an agent has everything needed to call and interpret it.

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% and the parameter description already explains that the value is a UUID or a yedapo.com episode URL with the UUID extracted. The description repeats none of that and adds no further meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('one episode's ... summary') plus the return format (markdown) and enumerates the payload fields (teaser, verdict, takeaways with timestamps, snippet, chapters, URL). The 'one episode' framing makes it distinguishable from the search_episodes sibling without opening either schema.

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 it when you already have a specific episode UUID or URL and want its full summary. There is no explicit statement of when to prefer this over search_episodes, and no prerequisites or exclusions are given.

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.

Resources