Skip to main content
Glama
Stripe Testing Tools MCP Server

Stripe Testing Tools MCP Server

by hideokamoto

Delete Stripe Test Products

delete_stripe_test_products
Destructive

Permanently delete Stripe test products by product ID or URL to clean up test data after integration testing.

Instructions

Permanently delete Stripe products for testing purposes

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_stripe_test_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoThe URLs of the products to delete
product_idsNoThe IDs of the products 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 safety is covered structurally; the description's contribution is the word "permanently", confirming irreversibility. It adds nothing about scope (test-mode only?), permission requirements, or what happens when both identifier sets are supplied.

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; the destructive qualifier appears first. It is only marginally under-specified rather than padded.

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 destructive, zero-required-parameter tool with no output schema, the description covers purpose and irreversibility but omits the identifier-selection rule and any confirmation or recovery guidance. Adequate, not complete.

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%, so both urls and product_ids are self-documented and the baseline applies. The description does not clarify the key semantic ambiguity the schema leaves open: whether these are alternative identifiers or both required, given that zero parameters are marked required.

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?

"Permanently delete Stripe products" is a specific verb plus resource, and "permanently" implicitly separates it from the archive_stripe_test_products sibling. It does not name that sibling explicitly, so the contrast requires an inference.

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" scopes it to test-mode data, but there is no statement of when to prefer this over archive_stripe_test_products or delete_stripe_test_customers, nor any precondition or warning gate before an irreversible action.

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