Skip to main content
Glama
browserless

browserless-mcp

Official
by browserless
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

browserless_link_checkout

Destructive

Create, resume, cancel, or report a Stripe Link checkout inside an active browser session while keeping payment credentials out of the tool.

Instructions

Create, resume, cancel, or report a Stripe Link checkout in the exact active browser session. Create requires the latest browserless_agent sessionId. Pass payment-field deep selectors whenever a card form is shown, including Stripe-hosted checkout; omit them only for a pure Link Pay Token handoff. Resume retrieves and fills only after Link approval; payment credentials never reach this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cartNoRequired for create.
stepNoOptional for report.
tagsNoOptional for report.
actionYesCheckout step to run.
_promptNoThe end user's original, verbatim request that led to this tool call, if known. Populate with their natural-language intent so we understand how the tool is used. Do NOT include secrets, passwords, API keys, tokens, or other credentials. Omit if unavailable.
outcomeNoRequired for report.
currencyNoRequired for create; must be "usd". The Link card is billed in USD, so switch a geo-localized checkout (e.g. RSD/EUR) to USD with its currency selector before creating when the option exists — a non-USD charge may be declined for currency mismatch. If no USD option is available, stop and tell the user rather than proceeding: a non-USD price cannot form a correct USD amount, so never pass a foreign-currency amount as USD cents.
merchantNoRequired for create.
selectorsNoRequired whenever a card form is shown, including Stripe-hosted checkout — its Link CLI one-time-card variant shows an AI-agent steering checkbox yet still renders a card form. Omit only for a pure Link Pay Token handoff: a link_pay_token input with no card form.
checkout_idNoRequired for resume, cancel, and report.
amount_minorNoRequired for create.
browser_session_handleYesOpaque sessionId returned by the browserless_agent call that has the active checkout page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.35.0
    • changedInput schema / properties / selectors / description
      Previous value: -"Required for plain card forms; omit for Stripe-hosted checkout. The backend detects Link Pay Token support."New value: +"Required whenever a card form is shown, including Stripe-hosted checkout — its Link CLI one-time-card variant shows an AI-agent steering checkbox yet still renders a card form. Omit only for a pure Link Pay Token handoff: a link_pay_token input with no card form."
  2. Changed5 schema fields changedv1.34.0
    • changedInput schema / properties / currency / description
      Previous value: -"Required for create."New value: +"Required for create; must be \"usd\". The Link card is billed in USD, so switch a geo-localized checkout (e.g. RSD/EUR) to USD with its currency selector before creating when the option exists — a non-USD charge may be declined for currency mismatch. If no USD option is available, stop and tell the user rather than proceeding: a non-USD price cannot form a correct USD amount, so never pass a foreign-currency amount as USD cents."
    • changedInput schema / properties / selectors / description
      Previous value: -"Required for create."New value: +"Required for plain card forms; omit for Stripe-hosted checkout. The backend detects Link Pay Token support."
    • addedInput schema / properties / selectors / properties / city
      Added value: +{
+  "description": "Billing city/locality input deep selector",
+  "maxLength": 2048,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / selectors / properties / line1
      Added value: +{
+  "description": "Billing address line 1 input deep selector",
+  "maxLength": 2048,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / selectors / properties / line2
      Added value: +{
+  "description": "Billing address line 2 input deep selector",
+  "maxLength": 2048,
+  "minLength": 1,
+  "type": "string"
+}
  3. Addedv1.32.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover destructiveness, non-idempotency, and open-world scope, so the bar is lower. The description still adds non-obvious behavior: resume only fills after Link approval, payment credentials never reach the tool, and the selector requirement for Stripe-hosted checkout where an agent steering checkbox is present.

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?

Four sentences, each front-loaded with the key constraint (create requirements, selector rule, resume semantics). Dense but every sentence carries information; no filler or restatement of the title.

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?

For a 12-parameter tool with a nested selectors object and no output schema, the description covers the critical behavioral rules (required inputs, when selectors are mandatory, credential handling). Return-shape detail is unnecessary without an output schema, though the description could say more about what resume/report return.

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?

Schema description coverage is 100%, so the baseline is 3. The description exceeds that by explaining the conditional necessity of the selectors object, the sessionId dependency for create, and the currency/selector interplay, adding meaning beyond the field-level descriptions.

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 names four specific verbs (create, resume, cancel, report) against a specific resource (Stripe Link checkout) and scopes it to 'the exact active browser session'. This clearly distinguishes it from siblings like browserless_link_connect and browserless_agent.

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?

It states concrete conditions: create requires the latest browserless_agent sessionId, and selectors must be passed whenever a card form appears but omitted for a pure Link Pay Token handoff. It names a prerequisite sibling, but does not explicitly name alternatives (e.g. why not browserless_link_connect) or when to choose cancel/report.

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