Skip to main content
Glama
Stripe Testing Tools MCP Server

Stripe Testing Tools MCP Server

by hideokamoto

Archive Stripe Test Products

archive_stripe_test_products
Destructive

Deactivate Stripe products for testing by archiving them via product IDs or URLs, keeping test environments clean and preventing use of outdated test products.

Instructions

Archive (deactivate) 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": "archive_stripe_test_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoThe URLs of the products to archive
product_idsNoThe IDs of the products to archive

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 safety profile is covered. The description adds real value by equating archive with 'deactivate' in parentheses, implying a non-permanent state change rather than erasure — but it never states whether the archive is reversible, what happens to products attached to active prices, or whether Stripe test-mode restrictions apply.

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 zero filler and the key clarification in parentheses. It is efficient, though the brevity edges toward under-specification rather than optimal concision.

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 two-parameter destructive tool with no output schema, the definition is minimally adequate: the action and target are clear. It omits how the two optional arrays relate and what a caller should expect after archiving, which matters for a mutation tool with no return-value documentation.

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%, with both 'urls' and 'product_ids' documented in the schema itself, so the description need not repeat them. The description adds no meaning about whether the two arrays are alternatives or can be combined, which the schema leaves ambiguous since both are optional.

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?

The description states a specific verb and resource ('Archive (deactivate) Stripe products') and clarifies the semantics of archiving via the parenthetical. It does not name or differentiate from the close sibling delete_stripe_test_products, so an agent cannot tell from the description alone why it would archive rather than delete.

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?

'for testing purposes' gives scope, but there is no when-to-use guidance and no mention of the obvious alternative, delete_stripe_test_products. Archiving versus deleting a product is a consequential choice that the description leaves entirely to inference.

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