LimeSurvey MCP Server

Import central participants

limesurvey_cpd_importParticipants

Import records into the central participant database.

Instructions

Import records into the central participant database.

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

Input Schema

Name	Required	Description	Default
`participants`	Yes	Central participant records.
`response_format`	No	Output format. JSON preserves the complete structured result; Markdown is optimized for reading.	json
`update_existing`	No	Update matching existing records.

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 cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), so the bar is lower. The description adds genuinely useful operational context the annotations do not: authentication uses the configured service account and the caller must not supply a session key. It still does not explain dedupe/matching behavior or interaction with update_existing.

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?

Two short sentences; the purpose is front-loaded and the auth constraint follows immediately. Nothing is wasted and there is no boilerplate.

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 and full parameter documentation, the description covers purpose and the non-obvious auth model. It leaves minor gaps: what key is used to match existing records, and what happens on duplicate/partial imports when update_existing is false.

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 three parameters (participants, response_format, update_existing) are already documented in the schema. The description adds no format, matching, or syntax detail beyond what the schema provides, which is the baseline 3.

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: 'Import records into the central participant database', which distinguishes the central participant database from survey-level token tables. It does not explicitly name the nearest sibling (limesurvey_add_participants) or state how this differs from it, 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?

Usage is implied by 'central participant database' but the description never says when to choose this over limesurvey_add_participants, limesurvey_add_participant, or limesurvey_validate_participants, and gives no prerequisites. No explicit when/when-not guidance is present.

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

Deploy Server