Skip to main content
Glama

delete_questions

Destructive

Remove one or more questions by ID in a batch operation. Deletes their answers while preserving the parent quiz or question bank; use only after explicit user confirmation.

Instructions

Delete one or more questions. DESTRUCTIVE. This is a BATCH operation.

    Pass `question_ids`, a list of obfuscated Skilljar question ids - a list even
    for one.

    The question's answers go with it. The parent quiz or question bank, and every
    other question in it, are UNTOUCHED.

    This is also the only way to change a question's answers, since they are
    immutable on update: delete and recreate.

    Requires `question-banks:write` OR `quizzes:write`, AND the `content.delete`
    capability, which is deliberately separate from `content.write` and is off in
    every profile except `full`. Take this action only on the user's explicit
    instruction.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
question_idsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
noteYes
totalYes
failedYes
succeededYes
Install Server

TDQS

A5/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses consequential side effects: answers are deleted along with the question, the parent quiz or question bank is untouched, and answers are immutable elsewhere. It also explains the security model with the separate content.delete capability, adding significant behavioral context for a destructive operation.

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?

Every sentence adds essential operational or safety information: batch semantics, ID format, cascade scope, the immutable-answers workflow, and required capabilities. The structure front-loads the destructive warning and keeps related details together without filler.

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

Completeness5/5

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

For a destructive, batch, security-sensitive tool, the description is complete: it covers the single parameter, side effects, exactly what is and is not deleted, required permissions, and the user-consent condition. An output schema exists, so return-value documentation is not needed here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it does so effectively. It explicitly names `question_ids`, states it must be a list even for one, clarifies the IDs are obfuscated Skilljar question IDs, and explains the cascade behavior affecting answers.

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 opens with 'Delete one or more questions,' a specific verb and resource, and immediately clarifies this is a BATCH operation. It also distinguishes the tool's scope from related delete tools by stating the parent quiz or question bank and every other question are untouched, so its purpose and boundaries are unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says this is the only way to change a question's answers because answers are immutable on update, providing clear guidance versus the update tool. It also states required capabilities and instructs to take the action only on the user's explicit instruction, giving both when-to-use and when-not-to-use context.

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

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/CloudSecurityAlliance/csa-skilljar'

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