Retrieve a recording's AI summary with TL;DR, key points, and action items. Returns current status if summary isn't ready yet.
Get a recording's AI summary: a TL;DR, key points, and any action items. If it isn't ready yet, returns the current status.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The recording's public id (the slug in its share URL, e.g. 'a1b2c3d4e5f6') or the full https://clipy.online/video/<id> URL. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that if the summary isn't ready, it returns the current status, adding behavioral context. With no annotations provided, this partially fulfills the transparency burden, but additional details (e.g., permissions, rate limits) are missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the main purpose and include a behavioral note. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema, the description adequately explains what is returned (summary components) and potential outcomes (status if not ready). It is sufficiently complete for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the 'id' parameter. The description adds meaning by explaining that the id can be the public slug or the full URL, which goes beyond the schema's description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a recording's AI summary including TL;DR, key points, and action items. It distinguishes from siblings like get_key_moments and get_transcript by focusing on the summary content.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when wanting the summary, but does not explicitly state when not to use it or mention alternatives. However, the purpose is clear and contextually differentiated from sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.