Skip to main content
Glama

unbind_quiz_question_banks

Destructive

Remove question banks from a quiz without deleting the banks. Pass quiz_id and question_bank IDs to unlink only the association, preserving the banks, their questions, and all other quizzes.

Instructions

Detach question banks from a quiz. The banks themselves are NOT deleted.

    Pass `quiz_id` and `question_banks`, a list of items each needing
    `question_bank_id`. Only the link is removed, permanently - the
    bank, its questions and every other quiz using it are untouched. The quiz keeps
    working with fewer questions.

    To delete the bank itself, use `delete_question_banks`. A bank not currently
    attached fails its own row with `not_found`.

    Requires the `quizzes:write` OAuth scope.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quiz_idYes
question_banksYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
noteYes
totalYes
failedYes
succeededYes
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds crucial nuance: only the link is removed permanently, while the bank, its questions, and other quizzes using it are untouched. It also discloses the OAuth scope requirement and per-row failure behavior, going well beyond the annotations.

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 four short paragraphs, front-loading the main action, then the critical non-destruction nuance, then usage routing, then auth. Every sentence earns its place and there is no 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 two-parameter destructive mutation with existing annotations and an output schema, this description is complete. It covers the action, side effects, auth requirement, alternative tool, and error behavior, leaving no meaningful gap for an agent deciding to call it.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate for the schema's lack of parameter documentation. It does compensate by explaining to pass quiz_id and question_banks as a list of items each requiring question_bank_id. This covers the essential shape, though it could have provided a bit more detail about the array item structure or additional allowed fields.

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 a specific verb and resource: 'Detach question banks from a quiz.' It immediately clarifies what is NOT deleted and distinguishes itself from the sibling delete_question_banks, so an agent can tell them apart without opening schemas.

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 when this tool should be used versus deleting a bank, names the alternative 'delete_question_banks', and even explains an error case where a bank is not currently attached. The agent receives clear routing 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