quiz_video_delete_templatePermanently delete a custom template you own. Quizzes that have a snapshot of this template are unaffected — the snapshot remains in their themeCustomization.
| Name | Required | Description | Default |
|---|---|---|---|
| templateId | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the destructiveHint annotation, it specifies that deletion is permanent, applies only to templates you own, and explicitly states that existing quiz snapshots remain in their themeCustomization. This adds real behavioral context about what is destroyed and what is preserved.
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 sentences, front-loaded with the core action and resource, followed by a single clarifying consequence. No wasted words, and the structure balances directness with necessary detail.
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 simple delete operation with one parameter and no output schema, the description covers permanence, ownership, and the non-obvious behavior regarding quiz snapshots. Annotations provide idempotency and destructive hints, making this fully adequate for an agent to select and invoke the tool.
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 single parameter templateId is self-explanatory from the schema and tool name, and the description adds the ownership requirement that gives context for the ID. However, schema coverage is 0%, so the description carries the burden and could have explicitly stated that templateId must refer to an owned template, though it already implies this.
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 a specific verb ('Permanently delete') and resource ('a custom template you own'), distinguishing it from sibling deletion tools like delete_quiz and delete_flashcard_deck. The ownership qualifier adds precision beyond the title.
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 when to use this tool (delete a template you own) and clarifies a key effect (snapshots in quizzes are unaffected), which informs whether the operation is safe. However, it does not explicitly contrast with alternatives like update_template or mention when not to use it, such as if a template is actively referenced.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct resource and action (create/get/list/update/delete per entity). Overlapping pairs like get_render vs download_render are clearly differentiated by their purpose, and generate_quiz vs create_quiz serve different creation modes. There is no ambiguity between tools.
The vast majority of tools follow a consistent 'quiz_video_<verb>_<noun>' pattern in snake_case. The only deviation is the three discovery tools (get_api_catalog, get_llms_txt, get_openapi_spec) which omit the 'quiz_video_' prefix, though they still use a clear verb_noun structure.
With 30 tools, the server is on the heavier side and exceeds the typical 15-tool guideline. However, the count is justified by the breadth of resources covered (quizzes, questions, hooks, templates, flashcard decks, renders, music, account) and each tool has a distinct role, so the size feels appropriate for a comprehensive API surface.
The server covers full CRUD for most core resources (quizzes, templates, flashcard decks, hooks) and add/list for questions. Minor gaps include no individual question update/delete and no direct render deletion, but these are not critical and the main workflows (create → view → render → download) are fully covered.