QuestionPunk

Question Delete

question_delete

Destructive

Delete a question, and display logic that depends on its answers. It works on published surveys too, where the question disappears for participants at once: confirm with the user before deleting from a survey that is collecting responses. A restore point is saved first (survey_version_restore, where this connection has it, can bring the question back). Needs surveyVersion = versions.current from survey_get; the result returns the next one.

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": {
      "surveyItemId": "<surveyItemId>",
      "surveyVersion": "<surveyVersion>"
    },
    "name": "question_delete"
  }
}

Input Schema

Name	Required	Description	Default
`surveyItemId`	Yes	Question ID (survey_items[].id from survey_get)
`surveyVersion`	Yes	Current survey version: versions.current from survey_get, or the surveyVersion your last edit returned. A stale version is rejected (WRONG_VERSION). The result returns the next one as surveyVersion.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructiveHint and openWorldHint, but the description adds real behavioral context: the question vanishes for participants immediately, a restore point is saved first, the call must be versioned, and the response returns the next version. This goes well beyond what the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and cascade, then layers caution and recovery info. It is dense but mostly earns its place; the parenthetical about restore is slightly convoluted but useful.

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, versioned mutation with an output schema, the description covers the important unknowns: live impact on published surveys, recovery mechanism, and version chaining. Return value details are correctly left to the output schema.

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 parameters are fully documented in the input schema, including the WRONG_VERSION rejection. The description restates the surveyVersion = versions.current requirement without adding new syntax or format detail, so baseline 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?

States a specific verb and resource ('Delete a question') and immediately names the cascade side effect ('display logic that depends on its answers'), which distinguishes it from question_update and the display_logic_* siblings that manage rules directly.

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?

Gives a clear conditional instruction ('confirm with the user before deleting from a survey that is collecting responses') and points to survey_version_restore as the recovery path. It does not explicitly contrast with alternative tools like question_update or display_logic_rule_delete, which keeps it from a 5.

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

All QuestionPunk tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?