LimeSurvey MCP Server

Activate survey

limesurvey_activate_survey

Activate a survey after LimeSurvey consistency checks. Requires confirm_activation=true.

Instructions

Activate a survey after LimeSurvey consistency checks. Requires confirm_activation=true.

Calls LimeSurvey RemoteControl method activate_survey. 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
`confirm_activation`	Yes	Required acknowledgement that survey activation changes its structure and behavior.
`activation_settings`	No	Optional activation settings such as anonymized, datestamp, ipaddr, ipanonymize, refurl, and savetimings.

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=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds useful behavioral context beyond annotations: activation occurs after consistency checks, explicit confirmation is required, the underlying RemoteControl method is named, and session-key authentication is explicitly excluded.

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?

The description is two tight paragraphs. The first front-loads the purpose and the required confirmation; the second adds implementation and authentication details. Every sentence contributes directly to correct invocation without padding.

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?

For a non-idempotent mutation tool with 4 parameters, an output schema, and annotations covering safety, the description covers purpose, required confirmation, consistency-check sequencing, authentication constraints, and the RemoteControl method. It could say more about failure modes if consistency checks fail, but it is largely complete given the structured data.

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, confirm_activation, response_format, and activation_settings in detail. The description repeats the confirm_activation=true requirement but adds no syntax, format, or default information beyond the schema, making the baseline 3 appropriate.

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?

The description states a specific verb and resource: 'Activate a survey'. It also adds the precondition 'after LimeSurvey consistency checks'. However, it does not distinguish this tool from the sibling limesurvey_activate_tokens beyond the resource name, so sibling differentiation is absent.

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 description provides an implied usage context ('after LimeSurvey consistency checks') and notes the required confirm_activation=true acknowledgement. It does not state when not to use this tool or name alternatives such as limesurvey_activate_tokens or limesurvey_add_survey, leaving routing to inference.

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

Deploy Server