LimeSurvey MCP Server

Export survey responses

limesurvey_export_responses

Read-onlyIdempotent

Export responses as a base64-encoded document.

Instructions

Export responses as a base64-encoded document.

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

Input Schema

Name	Required	Description	Default
`fields`	No	Optional response fields to export.
`survey_id`	Yes	Numeric LimeSurvey survey ID.
`heading_type`	No	Column heading style.
`document_type`	Yes	Export type such as csv, html, pdf, xls, or json.
`language_code`	No	LimeSurvey language code; null uses the survey default.
`response_type`	No	Answer text format.
`to_response_id`	No	Optional last response ID.
`response_format`	No	Output format. JSON preserves the complete structured result; Markdown is optimized for reading.	json
`from_response_id`	No	Optional first response ID.
`completion_status`	No	Completion filter.
`additional_options`	No

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

A3.7/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent profile, and the description adds real context on top: the response is base64-encoded (not raw content), it maps to the RemoteControl `export_responses` method, and it authenticates via a configured service account so no session key should be supplied. It omits any note about export size limits, timeouts, or long-running behavior, which is a modest gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the most differentiating fact — the base64-encoded output — front-loaded. The second sentence is slightly lower value but ties the tool to the upstream RemoteControl method name, which is useful for disambiguation; nothing is padded.

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-value explanation is unnecessary, and 91% schema description coverage carries the parameter burden. The remaining gap is the absence of any export-scoping or size guidance for a tool that can pull an entire response set.

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 91%, so the schema already documents nearly every one of the 11 parameters including the four enums. The description adds nothing about parameter syntax or interactions (e.g. how document_type relates to the base64 payload), so baseline 3 applies.

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 and resource ('Export responses') and pins down the output artifact as 'a base64-encoded document', which implicitly separates it from the limesurvey_export_responses_to_file sibling. It never names that sibling explicitly, so an agent must infer the inline-vs-file distinction rather than being told.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the by-token or to-file alternatives among the many export siblings. The usage is only implied by the output form (base64 payload returned inline rather than written to a file), which is thin for a fleet of near-duplicate export tools.

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

Deploy Server