LimeSurvey MCP Server

Delete survey

limesurvey_delete_survey

Destructive

Permanently delete a survey. Requires confirm_destructive_action=true.

Instructions

Permanently delete a survey. Requires confirm_destructive_action=true.

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

Input Schema

Name	Required	Description	Default
`survey_id`	Yes	Numeric LimeSurvey survey 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

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description still adds useful non-annotation context: the deletion is permanent, and authentication uses a configured service account rather than a caller-supplied session key (relevant given the get_session_key/release_session_key siblings). It stops short of saying what else is destroyed alongside the survey.

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?

Three short sentences, the destructive nature is front-loaded, and the confirmation precondition and auth note follow in order of importance. Nothing is padded or repeated.

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?

With an output schema present and annotations covering the safety profile, the description does not need to explain return values, and the auth clarification is a valuable addition. It is slightly incomplete in not warning that deleting a survey also removes its groups, questions, and responses.

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 survey_id, response_format, and confirm_destructive_action are all already documented in the schema. The description only restates the confirmation requirement, adding no syntax or format detail beyond the schema, which makes 3 the correct baseline.

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 states a specific verb and resource ('Permanently delete a survey'), and the resource is enough to separate it from the many sibling delete tools (delete_group, delete_question, delete_response, delete_participants, delete_quota). An agent can identify the target of the operation without opening the schema.

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?

It gives one concrete precondition ('Requires confirm_destructive_action=true'), which is real usage guidance, but there is no when-to-use vs when-not framing and no mention of alternatives or irreversibility tradeoffs relative to sibling operations.

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

Deploy Server