Skip to main content
Glama

Delete question group

limesurvey_delete_group
Destructive

Permanently delete a question group from a survey. Requires confirm_destructive_action to prevent accidental loss.

Instructions

Delete a question group from a survey. Requires confirm_destructive_action=true.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesNumeric question-group ID.
survey_idYesNumeric LimeSurvey survey ID.
response_formatNoOutput format. JSON preserves the complete structured result; Markdown is optimized for reading.json
confirm_destructive_actionYesRequired acknowledgement of the permanent deletion.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYes
resultYes
truncatedNo
truncation_messageNo
Behavior4/5

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

Description adds backend method name ('delete_group') and confirms destructive nature, consistent with destructiveHint annotation. No contradiction. Provides context beyond annotations about the required action confirmation.

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 sentences, front-loaded with purpose and key requirement, no fluff. Each sentence earns its place.

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?

Covers purpose, required parameter, auth, and backend. Missing preconditions or error scenarios, but output schema exists. Adequately complete given tool complexity.

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 coverage is 100%, so baseline is 3. Description only reiterates the confirm_destructive_action requirement without adding new semantic meaning to parameters beyond the schema.

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?

Clearly states deletion of a question group from a survey. Verb 'Delete' and resource 'question group' are explicit. Does not explicitly distinguish from sibling delete tools like limesurvey_delete_survey, but purpose is 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?

Mentions required parameter confirm_destructive_action=true and authentication method. Provides some usage context but no guidance on when to use vs alternatives (e.g., delete question vs group) or when not to use.

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/Wagner-Emden-IT-Services/limesurvey-mcp-server'

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