mcp-saas-toolkit

stripe_create_payment_link

Create a shareable payment link for a Stripe price. Customers can use the link to pay directly.

Instructions

Create a Stripe Payment Link for a given price. Returns a shareable URL that customers can use to pay.

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": {
      "price_id": "<price_id>"
    },
    "name": "stripe_create_payment_link"
  }
}

Input Schema

Name	Required	Description
`price_id`	Yes	The Stripe Price ID to create a payment link for (starts with price_)
`quantity`	No	Quantity of the item. Default: 1
`after_completion_url`	No	URL to redirect customers to after successful payment
`allow_promotion_codes`	No	Whether to allow promotion codes on this payment link

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Description states it creates a payment link and returns a URL, but with no annotations, it lacks details on side effects, permissions, or limits. Adequate but not thorough.

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 concise sentences with action and result front-loaded. No wasted words.

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?

Mentions return value (URL). Parameters are documented in schema. Lacks info on errors or rate limits, but adequate for a simple 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 coverage is 100%, so baseline is 3. Description adds no extra meaning beyond schema; 'for a given price' aligns with required price_id.

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?

Clear verb (create), resource (Stripe Payment Link for a given price), and outcome (returns a shareable URL). Distinguishes from sibling tools like stripe_create_invoice.

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 explicit guidance on when to use this tool versus alternatives like stripe_create_invoice or stripe_create_customer. No when-not-to-use information.

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