LimeSurvey MCP Server

Create survey

limesurvey_add_survey

Create an empty survey with minimum settings.

Instructions

Create an empty survey with minimum settings.

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

Input Schema

Name	Required	Description	Default
`title`	Yes	Title of the new survey.
`format`	No	Question display format: all, group-by-group, or single question.
`language`	Yes	Base language code for the survey.
`survey_id`	Yes	Desired survey ID. Use 0 to let LimeSurvey choose.
`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 mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds genuinely useful behavioral context: auth is via the configured service account and no session key should be supplied. The only weakness is the somewhat filler note about the underlying RemoteControl method name.

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, front-loaded sentences with the core purpose first and an operational note second. Little waste, though the RemoteControl method-name detail is marginally low-value.

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. The description covers purpose and the authentication prerequisite, which is what an agent needs to call it correctly; it could say a bit more about what 'minimum settings' defaults to, but nothing critical is missing.

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 all five parameters (including the survey_id=0 convention and response_format enum) are fully documented in the schema. The description adds no parameter-level meaning, which is the expected baseline 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 ('Create an empty survey with minimum settings'), and the 'empty'/'minimum settings' qualifier subtly separates it from import_survey, copy_survey, and create_survey_from_spec. It does not name those siblings explicitly, so differentiation is left partly to inference.

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 'empty survey with minimum settings' but there is no explicit when-to-use or when-not-to guidance. With several survey-creation siblings (import, copy, from_spec), the description never routes the agent between them.

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

Deploy Server