LimeSurvey MCP Server

Delete survey participants

limesurvey_delete_participants

Destructive

Delete participants by token-table row IDs. Requires confirm_destructive_action=true.

Instructions

Delete participants by token-table row IDs. Requires confirm_destructive_action=true.

Calls LimeSurvey RemoteControl method delete_participants. 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.
`token_ids`	Yes	Participant token-table row IDs.
`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 and idempotentHint=false, so the safety profile is covered. The description adds genuinely new context: the confirmation gate and the authentication model (configured service account, no session key), which the annotations do not convey.

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 short paragraphs, front-loaded with the action and target, followed by invocation and auth notes. Every sentence carries information an agent needs; nothing is padding.

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. The description covers targeting, confirmation, and auth adequately; it stops short of noting whether deletion cascades to associated responses or how partial failures among multiple token IDs are handled for this irreversible operation.

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, token_ids, and confirm_destructive_action are already documented. The description only restates the token-table row ID meaning, adding no syntax or constraints beyond the schema. 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?

State a precise verb+resource and scope: 'Delete participants by token-table row IDs.' This is immediately distinguishable from delete_survey, delete_response, and delete_group, and the ID-based targeting is explicit.

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 mandatory prerequisite (confirm_destructive_action=true) but gives no guidance on when to choose this over related operations, nor does it mention that token IDs typically come from list_participants. Usage is implied rather than framed.

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

Deploy Server