Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete form submission

delete_form_submission
Destructive

Permanently delete a form submission by its ID in a Cmssy workspace, removing submitted form data from the headless CMS when it is no longer needed.

Instructions

Permanently delete a form submission.

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": {
      "submissionId": "<submissionId>"
    },
    "name": "delete_form_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
submissionIdYesThe submission's id to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "submissionId"
      +]
  2. First observedv0.73.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known. The word 'Permanently' adds useful confirmation that the deletion is irreversible, going slightly beyond the annotations, but nothing is said about permissions, error behavior, or whether dependent data is affected.

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?

A single front-loaded sentence with no filler and the critical 'Permanently' qualifier in the leading position. It is arguably too terse rather than padded, so it loses a point only for underexplaining.

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 one-parameter destructive tool with full schema coverage and annotations covering the safety profile, the essentials are present. However, the description says nothing about the irreversibility workflow, required permissions, or failure modes, which matter for a permanent delete.

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?

With one parameter at 100% schema coverage, the schema already documents submissionId fully. The description adds no format, source, or retrieval guidance for the id, so 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 ('Permanently delete') and resource ('a form submission'), which separates it from siblings like get_form_submission, update_form_submission_status, and list_form_submissions. It does not explicitly name an alternative or scoping condition, but the action 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?

The phrase 'Permanently delete' implies this is for removal rather than archiving or status changes, which weakly distinguishes it from update_form_submission_status. There is no explicit when-to-use or when-not-to-use guidance and no reference to any sibling tool.

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