Delete Transcript By Id. Delete a previously generated transcript by its ID.
Bulk support: accepts transcription_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| transcription_id | Yes | ||
| transcription_ids | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly says 'Delete' (a destructive action) while the annotations set destructiveHint to false. This is a direct contradiction, making the description untrustworthy for behavioral expectations.
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 short and front-loaded, but the first sentence 'Delete Transcript By Id' is redundant with the tool name. The second sentence adds value, and the bulk note is useful.
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 description lacks essential context for a delete operation: no mention of return value (since no output schema), no indication of permanence or permissions, and the 'account' parameter is unexplained.
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?
The description explains transcription_id and transcription_ids, but completely ignores the 'account' parameter. With 0% schema coverage, it should describe all parameters to compensate.
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 deletes a transcript by its ID and mentions bulk support via transcription_ids, distinguishing it from other delete tools that target different resources.
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 context is clear: use this tool when you have a transcript ID to delete. No explicit alternatives or exclusions are needed given the specificity of the resource.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.