LimeSurvey MCP Server

Export survey statistics

limesurvey_export_statistics

Read-onlyIdempotent

Export survey statistics as a base64-encoded PDF, XLS, or HTML document.

Instructions

Export survey statistics as a base64-encoded PDF, XLS, or HTML document.

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

Input Schema

Name	Required	Description	Default
`language`	No	LimeSurvey language code; null uses the survey default.
`group_ids`	No	Optional group ID or list of group IDs.
`survey_id`	Yes	Numeric LimeSurvey survey ID.
`document_type`	No	Statistics document type.
`include_graphs`	No	Whether to include graphs.
`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

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is real: it discloses that the payload comes back base64-encoded rather than as a file, and that auth flows through the configured service account with no session key required.

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 tight sentences that front-load the purpose and then give the behavioral/auth note. No filler, though it stops just short of the routing detail that would make it maximally useful.

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 spelled out, and the description still conveys the result encoding (base64 PDF/XLS/HTML). Auth behavior is covered. Only the sibling-routing context is absent.

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 description does not elaborate on any parameter beyond the document types already enumerated in the schema. Per the baseline rule, a 3 is appropriate when the schema does the heavy lifting.

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 survey statistics') plus the output encodings ('base64-encoded PDF, XLS, or HTML document'). The 'base64-encoded' qualifier implicitly separates it from the sibling 'export_statistics_to_file', but that sibling is never named outright.

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?

Usage is only implied by the tool name; there is no explicit when-to-use statement or exclusion. It does supply one prerequisite ('do not provide a session key'), which nudges it above a bare 2, but the obvious alternative (limesurvey_export_statistics_to_file) is left unaddressed.

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

Deploy Server