LimeSurvey MCP Server

Generate a responsive LimeSurvey survey theme

limesurvey_generate_survey_theme

Create a validated GPL-2.0-or-later ZIP theme that inherits the official Bootstrap 5 vanilla theme for LimeSurvey 7 or 6.

Instructions

Create a validated GPL-2.0-or-later ZIP theme that inherits the official Bootstrap 5 vanilla theme for LimeSurvey 7 or 6. LimeSurvey installs the theme under the ZIP file name without .zip and dots: the result's installed_theme_name (for example acme_feedback-100-ls7), at most 45 characters. Upload the ZIP unrenamed and assign that name.

Input Schema

Name	Required	Description	Default
`title`	Yes	Human-readable title shown in LimeSurvey.
`author`	No		LimeSurvey MCP user
`density`	No		comfortable
`overwrite`	No
`author_url`	No
`font_style`	No		system
`text_color`	No		#1F2933
`theme_name`	Yes	Base name of the theme package, for example acme_feedback. LimeSurvey installs the package as installed_theme_name: <theme_name>-<theme_version without dots>-ls<major>, at most 45 characters.
`description`	No		Responsive survey theme generated with LimeSurvey MCP.
`focus_color`	No		#005FCC
`logo_base64`	No	Optional base64 PNG or JPEG logo without a data URL prefix.
`accent_color`	No		#C84B31
`author_email`	No
`primary_color`	No		#0B6B57
`surface_color`	No		#FFFFFF
`theme_version`	No		1.0.0
`logo_file_type`	No
`background_color`	No		#F5F7F6
`corner_radius_px`	No
`muted_text_color`	No		#52606D
`confirm_overwrite`	No
`content_max_width_px`	No
`target_limesurvey_major`	No		7

Output Schema

Name	Required	Description	Default
`result`	Yes
`workflow`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.6.0Oct 14, 2026

changedInput schema / properties / author_email / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

changedInput schema / properties / theme_name / description

Previous value: -"Unique LimeSurvey theme and folder name, for example acme_feedback."New value: +"Base name of the theme package, for example acme_feedback. LimeSurvey installs the package as installed_theme_name: <theme_name>-<theme_version without dots>-ls<major>, at most 45 characters."

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 the safety profile (non-read-only, non-destructive, non-idempotent, closed-world), so the bar is lower. The description still adds real behavioral context: the ZIP is validated, it inherits the official Bootstrap 5 vanilla theme, and critically that the installed name is derived from the ZIP filename (dots stripped, 45-char cap), which an agent must know before uploading.

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?

Three dense sentences, front-loaded with the deliverable and its version scope, followed by the naming rule and the upload instruction. No filler, though the installed-name formula appears twice (description and theme_name schema) without adding new information the second time.

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 described, and the description covers the artifact, naming derivation, and upload step. However, for a 23-parameter mutation tool with 13% schema coverage, it omits the overwrite/confirm_overwrite safety pairing and version-targeting semantics, leaving notable gaps for the caller.

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 only 13% across 23 parameters, so the description must compensate. It clarifies the two trickiest inputs, spelling out how theme_name plus theme_version map to installed_theme_name and citing the 45-character ceiling, but leaves overwrite/confirm_overwrite, target_limesurvey_major, and the styling parameters unexplained beyond their self-documenting defaults and patterns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and artifact ('Create a validated GPL-2.0-or-later ZIP theme') plus its inheritance basis (Bootstrap 5 vanilla theme) and target versions (LimeSurvey 7 or 6). This clearly separates it from siblings like limesurvey_validate_survey_theme and limesurvey_assign_survey_theme, which operate on themes rather than generating 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?

It implies a downstream workflow ('Upload the ZIP unrenamed and assign that name'), which points an agent toward the upload and theme-assignment tools, but it never states when to choose this tool over validate_survey_theme or how it relates to the publication guide. Usage is 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