Skip to main content
Glama

Delete form entries

delete_form_submissions
DestructiveIdempotent

Delete form inbox entries for good: every entry up to and including through (an entry id, such as a next_after of form_submissions), for example after you exported them. A full form takes new entries again once there is room. Repeating it deletes nothing more; delete_utility_data erases all entries but also gives the form a new address.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "through": 120,
      "instance_id": "frm_exampleexampleexample2"
    },
    "name": "delete_form_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
throughYesEntry id: this one and all older ones are deleted.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "frm_exampleexampleexample2",
      +    "through": 120
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed7 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
    • addedInput schema / properties / through / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "maxLength": 40,
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / through / maxLength
      Removed value: -40
    • removedInput schema / properties / through / type
      Removed value: -"string"
  3. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive and idempotent, yet the description adds value beyond them: it clarifies the deletion is limited to a range, that capacity is freed so a full form accepts entries again, and that the sibling alternative has a side effect (new address) this tool does not. Return format is not described, but no output schema exists and the operation's outcome is stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Reasonably short but the opening clause 'every entry up to and including through (an entry id, such as a next_after of form_submissions)' is awkward to parse and buries the key scope in parentheses. The final sibling comparison sentence is well placed, but the first sentence could be restructured for faster scanning.

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 three-parameter destructive tool with rich annotations and no output schema, the description covers range semantics, idempotency, capacity effects, and the alternative tool's differing side effect. The only minor gap is that entries newer than 'through' surviving is implied rather than stated.

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% and the schema already explains 'through' as 'this one and all older ones are deleted'; the description only adds that the value can be a next_after token, a marginal clarification. Baseline 3 is appropriate since the schema does the heavy lifting.

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 specific verb and resource ('Delete form inbox entries') plus a precise scope ('every entry up to and including through'), which an agent can distinguish from delete_utility_data without opening either schema.

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

Usage Guidelines4/5

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

Gives a concrete use case ('after you exported them') and explicitly contrasts with the sibling delete_utility_data, explaining that the sibling wipes everything but changes the form address. It stops short of an explicit 'do not use this when…' rule, but the alternative comparison effectively routes the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.