LimeSurvey MCP Server

Export response timeline

limesurvey_export_timeline

Read-onlyIdempotent

Return response counts by day or hour for a date range.

Instructions

Return response counts by day or hour for a date range.

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

Input Schema

Name	Required	Description	Default
`end`	Yes	End date/time accepted by LimeSurvey.
`start`	Yes	Start date/time accepted by LimeSurvey.
`period`	Yes	Timeline aggregation period.
`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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered externally. The description adds genuinely non-redundant behavior: it names the underlying RemoteControl method and specifies that the configured service account handles auth so no session key should be passed — useful given sibling get_session_key/release_session_key exist.

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, zero filler, purpose front-loaded first, then implementation/auth detail. Every sentence conveys distinct information.

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?

With an output schema present, return-value explanation is unnecessary, and the description correctly avoids it. It covers purpose, method provenance, and auth expectations for a 5-param read tool. It could add a note on what date formats are accepted (schema defers to 'accepted by LimeSurvey' vaguely), leaving a minor gap.

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 2 of 5 parameters are enums with documented values, so the schema carries the parameter semantics. The description restates only the period (day/hour) already encoded in the enum and adds no format or syntax detail beyond it; 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: 'Return response counts by day or hour for a date range.' An agent can distinguish this from sibling export tools like export_statistics and get_summary by the day/hour aggregation framing. It does not name those siblings explicitly, 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 Guidelines3/5

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

Usage is implied by the 'date range plus day/hour period' framing, but the description names no alternatives and gives no explicit when-to-use or when-not-to-use condition. The one actionable directive is negative-auth ('do not provide a session key'), which is guidance but not tool-selection guidance.

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

Deploy Server