LimeSurvey MCP Server

Update survey response

limesurvey_update_response

Update a response; include its response ID in the data.

Instructions

Update a response; include its response ID in the data.

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

Input Schema

Name	Required	Description	Default
`response`	Yes	Response fields, including the response ID, mapped to new values.
`survey_id`	Yes	Numeric LimeSurvey survey ID.
`response_format`	No	Output format. JSON preserves the complete structured result; Markdown is optimized for reading.	json

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

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is largely covered. The description adds genuinely useful operational context about service-account authentication and not supplying a session key, but it never says whether this is a partial merge or full replace of the response, which matters for a non-idempotent update.

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 sentences with the core action front-loaded and no wasted phrasing. The authentication caveat is tacked on as a compact second sentence and earns its place by preventing a common misuse.

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

Completeness3/5

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

With an output schema present, return values need not be explained, and annotations plus 100% schema coverage handle most of the burden. The remaining gap is the update semantics (merge vs replace) for a non-idempotent write, which the description does not address.

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%, and the schema's response property already states that the response ID is included in the fields, so the description's "include its response ID in the data" largely restates structured data. Baseline 3 is appropriate when the schema carries the parameter detail.

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?

States a specific verb+resource ("Update a response") and names the underlying RemoteControl method, so the operation is unambiguous. It does not explicitly distinguish itself from sibling write tools like limesurvey_add_response or limesurvey_delete_response, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use/when-not-to-use guidance and no alternatives named among the many sibling response tools. The only procedural hint is the requirement to include the response ID in the data, which is closer to a parameter note than usage guidance.

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

Deploy Server