Skip to main content
Glama

delete_question

DestructiveIdempotent

Remove a question from active survey content, with confirm: true. Moves the question (and any nested follow-ups) to recoverable survey trash — restore with edit_question.restore_from_trash.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question_id": "<question_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. The question (and any nested follow-ups) moves to recoverable survey trash, not permanent deletion — but requires explicit confirmation before removing it from the active survey.
question_idYesQuestion UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds the crucial behavioral detail that the question is not permanently destroyed: it moves to recoverable survey trash, and any nested follow-ups cascade with it. That cascade and recovery path are not derivable from the annotations or schema and materially change how an agent should reason about the 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?

A single compact sentence with the operation front-loaded, followed by the recovery consequence and the restore path. Nothing is wasted and no information is buried.

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 mutation tool with an output schema, annotations, and full schema coverage, the description covers the atomicity/recoverability question an agent actually needs answered before deleting. Nothing further about return values or parameters is required.

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?

Schema coverage is 100% and both required parameters (question_id, confirm) are fully documented in the input schema, including the must-be-true constraint on confirm. The description only restates "with confirm: true," adding no new syntax or semantics. Baseline 3 is the correct ceiling when the schema already does the work.

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 names a specific verb and resource ("Remove a question") and scopes it to "active survey content," which tells an agent that the deletion is a soft-removal from the active survey rather than a purge. It is distinguishable from siblings like delete_block or edit_question without opening a schema.

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

Usage Guidelines4/5

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

Usage is clearly implied: call this when a question should be taken out of active survey content, with the confirm flag required. It even names the recovery route (edit_question.restore_from_trash) which clarifies the reversible nature of the operation. It stops short of explicit guidance on when to use delete_question versus other delete siblings for adjacent resources.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources