LimeSurvey MCP Server

Get uploaded response files

limesurvey_get_uploaded_files

Read-onlyIdempotent

Return uploaded file metadata and base64 content for a token or response.

Instructions

Return uploaded file metadata and base64 content for a token or response.

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

Input Schema

Name	Required	Description	Default
`token`	Yes	Participant token.
`survey_id`	Yes	Numeric LimeSurvey survey ID.
`response_id`	No	Optional response 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

A3.7/5.0

Behavior4/5

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

Annotations already declare a safe read (readOnly, idempotent, non-destructive), but the description adds genuinely new behavioral context: authentication runs through the configured service account and no session key should be supplied. It also reveals that the payload contains base64 file content, hinting at potentially large responses, though it never states size or count limits.

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?

Front-loaded with the outcome and kept to three short sentences with minimal waste. The middle sentence restating the underlying RemoteControl method name largely duplicates the tool name, which is the one mildly redundant element.

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, and the auth model is covered explicitly. For a read-only lookup tool of this complexity the description is nearly sufficient, with only edge behavior (empty results, payload size) left unaddressed.

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 the parameters (token, survey_id, response_id, response_format) are already fully documented and the baseline is 3. The description only loosely maps to the token/response distinction and adds no format or value-semantics detail beyond the schema.

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 ("Return uploaded file metadata and base64 content") with the scope "for a token or response," which distinguishes it from the write-side sibling limesurvey_upload_file and the export tools. It does not explicitly name a sibling it is not, so it stops 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 Guidelines3/5

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

The phrase "for a token or response" implies the two lookup modes, giving an inferred sense of when each parameter applies. However, there is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives such as limesurvey_export_responses_by_token.

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

Deploy Server