Skip to main content
Glama

delete_quiz_item

Delete a question from a New Quiz in Canvas. Permanently removes the quiz item using course, assignment, and item IDs.

Instructions

Delete a question (item) from a New Quiz. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesThe quiz item ID to delete
course_idYesCanvas course ID
assignment_idYesThe assignment ID of the New Quiz
Behavior3/5

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

The description discloses that the action 'cannot be undone,' which is crucial behavioral context beyond the simple verb 'delete.' However, with no annotations provided, it doesn't disclose other potential effects like cascading impacts on student grades or quiz availability, leaving some behavioral uncertainty.

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?

The description is two short sentences, front-loaded with the action and resource, and the warning 'This cannot be undone' is placed prominently. Every word contributes, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete tool with full schema coverage, the description covers the essential purpose and irreversibility. However, it omits details such as whether the deletion requires specific permissions, whether the quiz must be unpublished, and what happens to student submissions, leaving some gaps for an agent.

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?

The input schema provides full descriptions for all three parameters (item_id, course_id, assignment_id), covering 100% of the schema. The description adds no additional parameter semantics beyond what the schema already contains, so the baseline score 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?

The description uses the specific verb 'Delete' and identifies the resource as 'a question (item) from a New Quiz,' clearly distinguishing it from sibling tools like delete_assignment or delete_module_item. It is concise and unambiguous.

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?

The description implies usage for deleting questions from New Quizzes, but it doesn't explicitly state when to choose this over alternatives or mention any prerequisites like quiz permissions. No exclusions are given, such as 'do not use for classic quizzes.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hughsibbele/Canvas-Agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server