Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

import_survey

Import a LimeSurvey survey file to create a new survey in the system. Upload a base64-encoded survey file and optionally name the imported survey.

Instructions

Import a LimeSurvey survey.

Args:
    survey_file: The survey file content (base64 encoded).
    survey_name: The name for the imported survey.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
survey_fileYes
survey_nameNo

Implementation Reference

  • main.py:413-422 (handler)
    The main handler function for the 'import_survey' MCP tool. It is decorated with @mcp.tool() which registers it, takes base64-encoded survey file and optional name, and delegates to the LimeSurvey client's import_survey method.
    @mcp.tool()
    def import_survey(survey_file: str, survey_name: str = None) -> int:
        """Import a LimeSurvey survey.
    
        Args:
            survey_file: The survey file content (base64 encoded).
            survey_name: The name for the imported survey.
        """
        with get_client() as client:
            return client.import_survey(survey_file, survey_name)
  • main.py:15-20 (helper)
    Helper function to create and return a LimeSurvey Client instance using environment variables, used by the import_survey tool.
    def get_client() -> Client:
        return Client(
            url=os.getenv("LIMESURVEY_URL"),
            username=os.getenv("LIMESURVEY_USERNAME"),
            password=os.getenv("LIMESURVEY_PASSWORD"),
        )
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It mentions 'import' which implies creation/mutation, but doesn't disclose permissions needed, whether it overwrites existing surveys, error handling, or output format. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence adds value, though the formatting with 'Args:' could be slightly more polished for front-loading.

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?

For a 2-parameter mutation tool with no annotations and no output schema, the description covers the basic operation and parameter meanings adequately. However, it lacks details on behavioral aspects like what happens on success/failure or the returned data structure, leaving gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaningful context for both parameters: 'survey_file' is clarified as 'base64 encoded' content (not just a file path), and 'survey_name' as 'the name for the imported survey'. With 0% schema description coverage, this significantly compensates by explaining what each parameter represents beyond their titles.

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 clearly states the action ('Import') and resource ('a LimeSurvey survey'), making the purpose immediately understandable. It distinguishes from siblings like 'add_survey' or 'copy_survey' by specifying import from a file, though it doesn't explicitly contrast them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'add_survey' or 'import_group'. The description only states what it does, not when it's appropriate or what prerequisites might be needed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/edgarrmondragon/limesurvey-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server