LimeSurvey MCP Server

Delete survey language

limesurvey_delete_language

Destructive

Remove a non-base language from a survey. Requires confirm_destructive_action=true.

Instructions

Remove a non-base language from a survey. Requires confirm_destructive_action=true.

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

Input Schema

Name	Required	Description	Default
`language`	Yes	Language code to remove.
`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.3/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotency, but the description adds real value beyond them: the mandatory destructive-acknowledgement flag and the authentication model ('configured service account; do not provide a session key'). It could go further by stating that removal is irreversible and what happens to translations tied to that language.

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, front-loaded with purpose and the blocking prerequisite, with no redundant restatement of the tool name. Every sentence earns its place.

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 four-parameter tool with an output schema and rich annotations, the description covers purpose, the safety gate, and the auth expectation. Return values are handled by the output schema, so nothing required to invoke it correctly is missing.

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, language, response_format, and confirm_destructive_action are all documented in the schema itself. The description only restates the confirm flag requirement and adds no semantics for the other parameters, matching the baseline for a fully-covered schema.

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 ('Remove a ... language from a survey') and narrows the scope with 'non-base', which separates it from limesurvey_add_language and limesurvey_set_language_properties. An agent can identify the operation without opening any schema.

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 precondition ('Requires confirm_destructive_action=true') and an implicit exclusion via 'non-base language', so the agent knows base languages are out of scope. It stops short of explicitly routing to a sibling (e.g. set_language_properties for edits), so it is not a full when/when-not/alternative statement.

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

Deploy Server