mcp-saas-toolkit

stripe_list_products

Lists active Stripe products with prices. Helps browse catalog or find Price IDs for payment links.

Instructions

List Stripe products with their prices. Useful for browsing your catalog or finding Price IDs for payment links.

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": "stripe_list_products"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of products to return (1-100). Default: 20
`active`	No	Only return active products. Default: true

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 29, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so description carries the burden. It states the action (list) and the data included (prices) but does not mention pagination, authentication, or rate limits. For a read-only list operation, this is adequate but not rich.

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

Conciseness5/5

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

Two short sentences, no wasted words. Purpose and usage are front-loaded. Highly concise.

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?

No output schema, but description indicates it returns products with prices. For a simple list tool, this is sufficient. However, could be improved by noting the return structure or pagination behavior.

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?

Input schema covers both parameters (limit, active) with descriptions, achieving 100% coverage. Description adds no extra meaning beyond the schema, so baseline of 3 is appropriate.

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?

Description clearly states verb 'List' and resource 'Stripe products with their prices', which distinguishes it from sibling tools like stripe_list_customers. It also mentions specific use cases (browsing catalog, finding Price IDs), adding clarity.

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?

Provides context on when to use the tool ('browsing your catalog or finding Price IDs for payment links'). Implicitly distinguishes from other Stripe tools but lacks explicit exclusion statements.

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