Skip to main content
Glama
OuattaraTech

kobotoolbox-mcp-server

by OuattaraTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete KoboToolbox Form

kobo_delete_form
DestructiveIdempotent

Permanently delete a KoboToolbox form and all its submissions. Requires explicit confirmation and exact submission count to prevent accidental data loss.

Instructions

Permanently delete a form AND ALL ITS SUBMISSIONS. THIS CANNOT BE UNDONE.

Args:

  • uid (string): asset uid of the form to delete

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

  • confirm_submission_count (number): required when the form has submissions — pass the exact count, to prove the data loss is intended

Don't use when: you just want to stop collecting data. Use kobo_archive_form instead — it keeps every response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesAsset uid of the form to permanently delete
confirmYesMust be explicitly set to true to confirm this irreversible deletion
confirm_submission_countNoRequired when the form has submissions: pass the exact number reported by kobo_list_forms, to prove the data loss is intended.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses the permanent, destructive nature of the operation, including that submissions are deleted too and that the action cannot be undone. This goes beyond the destructiveHint annotation by specifying the exact data-loss scope and the confirmation safeguard.

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?

The description is concise, front-loads the critical warning, uses a clear argument list, and ends with a practical alternative. Every sentence earns its place without unnecessary filler.

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 destructive tool with no output schema, the description fully covers the operation's consequences, the required confirmation parameters, the submission-count safeguard, and the appropriate alternative. An agent has enough context to invoke it safely.

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?

The input schema already has 100% description coverage for all parameters, so the baseline is 3. The tool description mostly restates the schema's parameter explanations without adding new semantic detail or clarifying constraints beyond what is already present.

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 uses a specific verb ('delete'), names the resource ('form'), and explicitly includes all submissions with irreversible consequences. It also distinguishes itself from the sibling kobo_archive_form, so the agent can tell them apart immediately.

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?

It gives an explicit when-not-to-use rule: 'Don't use when: you just want to stop collecting data. Use kobo_archive_form instead — it keeps every response.' This clearly routes agents away from destructive deletion when archiving is the intended behavior.

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