LimeSurvey MCP Server

List administration users

limesurvey_list_users

Read-onlyIdempotent

List administration users, optionally filtered by ID or username.

Instructions

List administration users, optionally filtered by ID or username.

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

Input Schema

Name	Required	Description	Default
`user_id`	No	Optional administration user ID.
`username`	No	Optional administration username.
`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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: it names the underlying RemoteControl method and states that authentication comes from the configured service account with no session key required. It does not discuss result size or return handling, but the output schema covers that.

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 tight sentences with the core capability front-loaded in the first few words. The second sentence is implementation/auth detail that has some value but is slightly meta relative to pure usage selection.

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 rich annotations, 100% schema coverage, and an output schema, the remaining burden is light and this description covers the auth model that the structured fields do not. Nothing essential to invoking it correctly is missing, though a note on result volume or ordering would round it out.

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 every parameter including the response_format enum is already documented with its default and effect. The description's "optionally filtered by ID or username" merely restates the schema without adding format, matching, or precedence rules, so the baseline of 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 ("List administration users") plus the optional filter dimensions, so an agent can distinguish it from limesurvey_list_participants and the other list_* siblings. It stops short of explicitly naming a contrasting sibling, but the resource is precise enough to be unambiguous.

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 conveys that filtering is optional, implying "use with no params for all users, or narrow by ID/username," which is usable guidance. However, it never states when to prefer this over an alternative lookup path or any prerequisites, so guidance remains implied rather than explicit.

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

Deploy Server