Skip to main content
Glama
Stripe Testing Tools MCP Server

Stripe Testing Tools MCP Server

by hideokamoto

Delete Stripe Test Customers

delete_stripe_test_customers
Destructive

Permanently delete Stripe test customers by ID to clean up test data and reset customer records for Stripe integration testing.

Instructions

Permanently delete Stripe customers for testing purposes

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": {
      "customer_ids": "<customer_ids>"
    },
    "name": "delete_stripe_test_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idsYesThe IDs of the customers to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the risk profile is supplied structurally; 'Permanently' only reinforces irreversibility. The description says nothing about cascade effects (e.g., attached subscriptions), partial-failure behavior in a batch ID list, idempotency, or required API credentials — meaningful gaps for a destructive batch operation.

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?

One short, front-loaded sentence with no redundant wording. It is efficient, though the terseness leaves no room for the operational caveats this destructive tool needs.

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?

The tool is simple — one documented parameter, no output schema, and annotations that already carry the destructive safety signal. Adding cascade/partial-failure notes would improve it, but nothing essential to invoking it correctly is missing.

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 description coverage is 100% for the single parameter and it is clearly documented as 'The IDs of the customers to delete'. The description adds no meaning beyond that, 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 and resource ('Permanently delete Stripe customers') plus a scope qualifier ('for testing purposes'). It is distinguishable from the sibling product/clock tools by resource name alone, though the description itself does not draw that contrast explicitly.

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

Usage Guidelines2/5

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

The phrase 'for testing purposes' implies a test-mode context but gives no explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g., whether non-test customers are rejected, whether this should follow create_stripe_test_customers cleanup). No alternative is named.

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