LimeSurvey MCP Server

Delete question

limesurvey_delete_question

Destructive

Delete a question from its survey. Requires confirm_destructive_action=true.

Instructions

Delete a question from its survey. Requires confirm_destructive_action=true.

Calls LimeSurvey RemoteControl method delete_question. Authentication uses the configured service account; do not provide a session key.

Input Schema

Name	Required	Description	Default
`question_id`	Yes	Numeric question ID.
`response_format`	No	Output format. JSON preserves the complete structured result; Markdown is optimized for reading.	json
`confirm_destructive_action`	Yes	Required acknowledgement of the permanent deletion.

Output Schema

Name	Required	Description	Default
`method`	Yes
`result`	Yes
`warnings`	No
`truncated`	No
`truncation_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.0Oct 14, 2026

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "$ref": "#/definitions/__schema0"
+  },
+  "type": "array"
+}

First observedv1.3.1Jul 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful operational context beyond annotations: it requires explicit confirmation and states that authentication uses the configured service account, with no session key needed.

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 short, front-loaded with the destructive action, and every sentence adds operational value. There is no wasted wording or redundant explanation.

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

Completeness4/5

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

Given the rich annotations, full schema coverage, and an output schema, the description is complete enough for correct invocation. It covers the destructive nature, confirmation requirement, and authentication approach, though it could mention irreversible effects more explicitly.

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 description coverage is 100%, so the schema already documents question_id, confirm_destructive_action, and response_format. The description mainly repeats the confirmation requirement and adds authentication guidance rather than adding parameter-specific syntax or semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: delete a question from its survey. It is distinct from sibling tools like replace_question or update_question_from_spec, though it does not explicitly name those alternatives.

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 gives a required precondition (confirm_destructive_action=true) but does not explain when to choose deletion over alternatives such as replacing or updating a question. Usage is implied by the tool name and purpose, which is the minimum viable level.

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

Deploy Server