LimeSurvey MCP Server

Activate participant table

limesurvey_activate_tokens

Create the survey participant table and optional custom attributes.

Instructions

Create the survey participant table and optional custom attributes.

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

Input Schema

Name	Required	Description	Default
`survey_id`	Yes	Numeric LimeSurvey survey ID.
`response_format`	No	Output format. JSON preserves the complete structured result; Markdown is optimized for reading.	json
`attribute_fields`	No	Additional participant attribute field numbers.

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.5/5.0

Behavior3/5

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

The description usefully adds auth context beyond annotations ('uses the configured service account; do not provide a session key') and names the underlying RemoteControl method. However, with idempotentHint=false it does not explain what happens on repeated activation, nor does it disclose side effects such as replacing/locking participant data — meaningful gaps for a table-creating mutation.

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 action front-loaded and the auth constraint placed second. No filler; every sentence carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 annotations carry the safety profile. Still, for a mutation that creates the participant table, the description omits prerequisites and the consequence of re-running, leaving the definition only minimally complete.

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 schema already documents survey_id, response_format, and attribute_fields. The description's mention of 'optional custom attributes' loosely maps to attribute_fields but adds no syntax or format detail beyond the schema, making the baseline 3 correct.

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 the survey participant table and optional custom attributes.' An agent can distinguish this from sibling operations like get_participant_table_status or add_participants, though it never explicitly contrasts with them.

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 purpose ('create the table'). There is no explicit when-to-use guidance, no mention of preconditions (e.g. that the survey must exist or that the table must not already be active), and no reference to the related sibling limesurvey_get_participant_table_status that would help an agent decide.

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

Deploy Server