Skip to main content
Glama

List questions

limesurvey_list_questions
Read-onlyIdempotent

List questions and subquestions in a survey or group.

Instructions

List questions and subquestions in a survey or group.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "survey_id": "<survey_id>"
    },
    "name": "limesurvey_list_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idNoOptional question-group ID.
languageNoLimeSurvey language code; null uses the survey default.
survey_idYesNumeric LimeSurvey survey ID.
response_formatNoOutput format. JSON preserves the complete structured result; Markdown is optimized for reading.json

Output Schema

NameRequiredDescriptionDefault
methodYes
resultYes
warningsNo
truncatedNo
truncation_messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "$ref": "#/definitions/__schema0"
      +  },
      +  "type": "array"
      +}
  2. First observedv1.3.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds a genuinely useful operational detail — that auth uses the configured service account and no session key should be passed — but says nothing about result size, pagination, or ordering for a listing call.

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 tight sentences: the purpose is front-loaded and the auth caveat follows. Nothing is padded or redundant.

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 read-only listing tool with a fully described schema, complete annotations, and an output schema covering return values, the definition is nearly sufficient. The only gap is the absence of any note about ordering or result volume for potentially large question lists.

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% and documents all four parameters (group_id, language, survey_id, response_format) with enums and nullability. The description only restates the survey/group scoping already in the schema, adding no format or semantics beyond it, so the baseline 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 questions and subquestions') plus the scoping dimensions (survey or group). It is clearly distinguishable from mutation siblings like delete_question or set_question_properties, but it does not explicitly contrast itself with the closest read sibling, get_question_properties.

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 mention of 'in a survey or group' implies when the tool is applicable and which identifier to supply, but there is no explicit guidance on when to choose this over get_question_properties or get_fieldmap, and no prerequisites are stated beyond the auth note.

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

Deploy Server

Other Tools