Skip to main content
Glama
OuattaraTech

kobotoolbox-mcp-server

by OuattaraTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete KoboToolbox Submissions

kobo_delete_submissions
DestructiveIdempotent

Permanently delete specific form submissions after confirmation. Use to remove test entries, duplicates, or responses respondents asked to withdraw. Cannot be undone.

Instructions

Permanently delete specific submissions from a form. THIS CANNOT BE UNDONE.

Use it to remove test entries, duplicates, or a response a respondent asked to withdraw.

Args:

  • uid (string): asset uid of the form

  • submission_ids (array of strings): the "_id" values from kobo_list_submissions

  • confirm (true): must be explicitly set to true

Don't use when: you want to discard a whole form's data — that is kobo_delete_form. To merely flag bad rows while keeping them, use kobo_validate_submissions with 'not approved' instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesAsset uid of the form
confirmYesMust be true — deleted submissions cannot be recovered
submission_idsYesIds of the submissions to permanently delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true and readOnlyHint=false; the description adds the irreversible nature ('THIS CANNOT BE UNDONE') and clarifies exactly what is destroyed (specific submissions, not the whole form). This adds useful context beyond the annotations.

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?

Well-structured and front-loaded with the critical warning, then use cases, parameters, and exclusions. Every sentence earns its place and the description is compact without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with no output schema, the description covers purpose, parameter provenance, required confirm flag, alternatives, and destructive consequences. Nothing essential for an agent to call it correctly is missing.

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?

Schema coverage is 100%, so the schema already documents all parameters. The description adds extra meaning by telling the agent that submission_ids should be the '_id' values from kobo_list_submissions and that confirm must be explicitly true, going beyond the schema text.

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?

States a precise verb and resource: 'Permanently delete specific submissions from a form.' It clearly distinguishes itself from sibling kobo_delete_form (whole form deletion) and kobo_validate_submissions (flagging instead of deleting), so an agent can tell them apart.

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

Usage Guidelines5/5

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

Explicitly lists when to use it: remove test entries, duplicates, or a withdrawal request. It also gives explicit 'Don't use when' conditions with named alternatives, leaving no ambiguity about tool selection.

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