pifini

Create ticket checkout link

create_ticket_checkout

Create a secure Stripe-hosted payment link for event tickets. Returns a checkout URL — give it to the human to complete payment themselves; tickets with QR codes are emailed after payment. Get ticket_type_id values from get_event. Always confirm the exact tickets and total with the human before calling this.

Input Schema

TableJSON Schema

Name	Required	Description
`items`	Yes	Ticket selections
`buyer_name`	No	Buyer's name (optional)
`event_slug`	Yes	Event slug
`buyer_email`	Yes	Email to deliver tickets to (required — ask the human)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`event`	No
`total`	No
`currency`	No
`order_id`	No
`checkout_url`	No
`instructions`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "checkout_url": {
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "event": {
+      "type": "string"
+    },
+    "instructions": {
+      "type": "string"
+    },
+    "order_id": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedJul 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds context beyond annotations: describes the payment flow (returns URL, tickets emailed after payment), which is consistent with the readOnlyHint=false and destructiveHint=false annotations.

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?

Three concise sentences with no waste, front-loaded with the core purpose.

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

Completeness5/5

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

Covers all aspects: input, output (checkout URL), side effects (email after payment), and prerequisites (get_event), making the tool self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description adds value by clarifying the buyer_email is required and should be asked from the human, and that ticket_type_id comes from get_event.

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?

Clearly states the tool creates a Stripe-hosted payment link for event tickets, distinguishing it from sibling tools like get_event which are read-only.

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?

Explicitly advises confirming ticket details with the human before calling and references get_event for ticket_type_id, but does not explicitly state when not to use.

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

All pifini tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?