Skip to main content
Glama

Rendreal

Create a payment link

order_create_payment_link
Destructive

Create a Stripe embedded-checkout link for an existing order, only when the customer asks to pay.

The link locks the order to its design for good, so never create it just because the customer picked or finished a design.

Only for orders created in this session (OrderNotInSessionError otherwise) — an order someone mentions or that order_lookup found cannot be paid here, so offer to escalate rather than retrying.

Attaches each item's design to its own item once every item is covered. Each item needs a design or artwork with a submitted page mapping. Uses each design's latest snapshot, so the customer gets the version they last refined. Do NOT call order_attach_design yourself, even on an order with several items. Attaching is irreversible upstream, and doing it earlier locks the order onto a draft the customer has since edited. A file uploaded for an item after its design, before the attach, replaces that design.

Every line must carry artwork before the order can be paid (ArtworkRequiredError otherwise) — either a design (attached here, at order_create time, or via order_attach_design) or a finished artwork file uploaded through order_get_artwork_upload_page. A multi-item order is one Stripe checkout, so a multi-line cart is payable once each line is covered. DesignRenderFailedError means an attached design's print file failed to render. The design on this order cannot be changed, so no retry here helps; the reason says how to place a new order. NoSnapshotError means the session's design is not saved yet; a photo book can take a few minutes after it resolves. Wait a little and call this again. After 5 tries without a saved design it becomes ArtworkStillRequiredError.

Returns a job — poll until SUCCEEDED for the checkout_url. Put checkout_url in your reply as a markdown hyperlink (never the raw URL), and call order_get yourself to confirm payment. When the payment card is displayed, it shows a "Pay securely" button wired to the link and polls order_get itself once clicked, so just confirm the payment step is ready and share the link again only if the customer asks for it.

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": {
      "session_id": "<session_id>",
      "order_id": "<order_id>"
    },
    "name": "order_create_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes
session_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations: it discloses that the link irreversibly locks the order to its design, that attaching happens implicitly per item, and it enumerates named failure modes (OrderNotInSessionError, ArtworkRequiredError, DesignRenderFailedError, NoSnapshotError, ArtworkStillRequiredError) with what each means and whether retrying helps. It also explains the async job return and the UI behavior behind the returned link, consistent with destructiveHint=true.

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?

The critical guardrail is front-loaded in the first two sentences and the structure moves logically from when-to-use to preconditions to errors to output handling. It is dense and long, but nearly every sentence carries an operational constraint rather than filler.

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 everything an agent needs for a side-effecting, async, error-prone operation: preconditions, implicit side effects, per-error recovery guidance, job polling, and how to present the checkout_url. The output schema exists, yet the description still adds the presentation rule (markdown hyperlink, never raw URL) and the order_get confirmation step.

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 0%, so the description carries the burden. It does clarify which order_id values are valid ('orders created in this session,' not ones found via order_lookup), but it never names or explains session_id and gives no format details for either parameter.

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?

Opens with a specific verb and resource: 'Create a Stripe embedded-checkout link for an existing order.' It also scopes the action to a customer-requested payment, which cleanly separates it from order_attach_design, order_get, and order_lookup, all of which are named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when ('only when the customer asks to pay') and when-not ('never create it just because the customer picked or finished a design'), plus an alternative for out-of-scope orders ('offer to escalate rather than retrying'). It even pre-empts a tempting wrong call: 'Do NOT call order_attach_design yourself.'

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources