Skip to main content
Glama

bulk_delete_coupon

DestructiveIdempotent

Delete the SAME coupon code across many apps in one call: the inverse of bulk_create_coupon, for retiring a portfolio-wide promo. WRITE, human-gated: a real delete requires an elicitation-capable client; the human sees every app the code would be removed from (with per-app redemption counts) and must click approve, and confirm_used is only consulted for dry_run previews. Clients without elicitation are refused UNLESS the deployment sets SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 and the call passes confirm_write:true, which is how Claude Code and cron reach these writes; dry_run still works anywhere. An app that never had the code is reported skipped rather than failing the batch, since the desired end state already holds there. Returns a per-app outcome matrix plus deleted/skipped/failed counts. Use dry_run:true first to see exactly which apps would lose the code. Pass explicit app_ids (from list_apps) so a delete can't hit an app you didn't name.

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": {
      "app_ids": "<app_ids>",
      "code": "<code>"
    },
    "name": "bulk_delete_coupon"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
app_idsYes
dry_runNo
confirm_usedNo
confirm_writeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm_write
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/readOnlyHint annotations: it discloses the elicitation requirement, the human-approval flow with per-app redemption counts, the SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 plus confirm_write:true escape hatch for non-elicitation clients, and that dry_run works anywhere. It also states the return shape (per-app outcome matrix plus deleted/skipped/failed counts).

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?

Front-loaded with the core action and its inverse, then layers the gating and runtime details. Dense but nearly every clause carries required information; the elicitation/env-var sentence is long but justified given how much it changes agent behavior.

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, human-gated bulk mutation with no output schema, the description covers preconditions, approval mechanics, skip semantics, return values, and a safe preview path. An agent has everything needed to call it correctly or fall back to dry_run.

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?

With 0% schema description coverage the description must carry all five parameters, and it does explain app_ids provenance, dry_run preview behavior, and the confirm_write escape hatch. The confirm_used explanation ('only consulted for dry_run previews') is terse and slightly ambiguous about what it actually confirms, leaving a small gap.

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 with explicit scope ('the SAME coupon code across many apps in one call') and positions itself as the inverse of bulk_create_coupon, which cleanly separates it from delete_coupon and bulk_create_coupon in the sibling list.

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 clear operational guidance: run dry_run:true first, pass explicit app_ids sourced from list_apps, and notes that apps lacking the code are skipped rather than failing. It names the sibling it inverts but never explicitly routes single-app deletions to delete_coupon, leaving one alternative implicit.

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.

Resources