Skip to main content
Glama
Sign In
stripe-mcp-server

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Price

create_price

Create a new price for a Stripe product by specifying product ID, unit amount in smallest currency unit, and currency code. Optionally set recurring billing intervals or metadata.

Instructions

Create a new price for a product.

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": {
      "product": "<product>",
      "unit_amount": "<unit_amount>",
      "currency": "<currency>"
    },
    "name": "create_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct ID (prod_...)
unit_amountYesPrice in smallest currency unit (e.g. 1000 = $10.00)
currencyYesCurrency code (e.g. "usd")
recurringNoRecurring config (omit for one-time price)
activeNoWhether price is active
metadataNoMetadata
nicknameNoInternal nickname
idempotency_keyNoOptional idempotency key for safe retries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

The description 'Create a new price for a product' implies a mutation but adds no behavioral traits beyond the verb. Annotations are absent, so the description carries full burden; yet it does not disclose idempotency, side effects, or error scenarios. Minimal transparency.

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?

Single sentence, no redundancies. However, given the tool's complexity (8 params, nested objects), the description is perhaps too brief to be fully informative, slightly limiting conciseness score from 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool requires nested objects (recurring), multiple required fields, and no output schema. The description provides zero context about return value, error cases, or behavior for one-time vs. subscription prices. Incomplete for a creation tool.

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%, so parameters are well-documented in the schema. The description adds no further meaning or examples, meeting the baseline for high coverage.

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?

The description clearly states the verb 'create' and resource 'price for a product', exactly matching the tool name. Among sibling tools like create_product or create_coupon, this distinguishes the tool's purpose unambiguously.

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?

No guidance on when to use this tool vs. alternatives like create_product or when not to use it. No prerequisites (e.g., product must exist) or context about idempotency key usage. The description is silent on usage conditions.

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

Deploy Server

Other Tools