LimeSurvey MCP Server

Delete question group

limesurvey_delete_group

Destructive

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

Instructions

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

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

Input Schema

Name	Required	Description	Default
`group_id`	Yes	Numeric question-group ID.
`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, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it names the underlying RemoteControl method and clarifies that auth uses the configured service account with no session key supplied, which is non-obvious given the sibling session-key tools. It omits whether contained questions are cascaded/removed with the group, the one notable behavioral gap.

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?

Two sentences plus a short auth note, with the action and precondition front-loaded and zero filler. Every sentence carries information the agent cannot get elsewhere.

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?

An output schema exists, so return values need not be explained, and annotations plus the auth/method notes cover the operational essentials. The gap is that a destructive group deletion does not mention the fate of questions inside the group, which an agent might reasonably need before confirming.

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, group_id, response_format, and the confirm flag are all documented in the schema itself. The description only restates the confirm flag requirement, adding no syntax or constraint detail beyond what the structured fields provide; 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 group from a survey), which cleanly distinguishes it from siblings like limesurvey_delete_survey, limesurvey_delete_question, and limesurvey_set_group_properties. An agent can identify 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?

The description states the precondition that confirm_destructive_action=true is required, which is useful gating context. However, it gives no guidance on when to choose this over alternatives (e.g., set_group_properties to modify rather than remove) and no exclusions or consequences of proceeding.

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

Deploy Server