list_draftsRetrieve drafts for the current podcast publication, with pagination, result limits, and optional filters, so you can review staged episodes before publishing.
List drafts for the current publication.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max number of drafts to return. | |
| filter | No | Filter string, defaults to "draft". | draft |
| offset | No | Pagination offset. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not mention read-only/safety traits, pagination behavior, permissions, or rate limits; it only adds the 'current publication' scope.
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?
The description is a single front-loaded sentence with no filler. It is appropriately concise, though its brevity contributes to gaps elsewhere.
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?
The tool is simple, has an output schema, and has complete parameter schema coverage, so the description needn't explain return values or parameter details. However, it still lacks enough usage and behavioral context for an agent to confidently choose it over sibling draft tools.
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 description coverage is 100%, so the schema already explains limit, filter, and offset. The description adds no parameter semantics beyond the schema, which matches the baseline for fully documented parameters.
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?
States a specific verb (List) and resource (drafts) and scopes it to the current publication. It does not explicitly distinguish itself from nearby tools like get_draft, but the basic purpose is clear.
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 gives no explicit when-to-use guidance, no exclusions, and no alternatives. An agent must infer that this is the bulk-listing tool versus get_draft or list_publications.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.