Skip to main content
Glama

Pagetool

Create a client pay link

create_client_checkout

Creates a pay link (pay_url) for a business owner with NO Pagetool account: they pay by card (US cards only) a monthly subscription (default $25/month, or price_cents) that registers the domain, keeps it renewed and puts the site live on it automatically. If they cancel, or stay unpaid past the grace period, the site comes down. The link expires at expires_at. Signed-in accounts only. Free to create; it never charges you. A refused or unchecked domain ending carries reason and a plain reason_text: unsupported or price_unavailable mean we do not sell that ending right now; lookup_failed or cap_reached mean it was NOT checked, so search again, and never tell the customer we do not sell 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": {
      "site_key": "<site_key>",
      "domain": "<domain>"
    },
    "name": "create_client_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to register for them, bare, e.g. "joesbakery.com". Must be available; .com/.net/.org and other Cloudflare endings for now.
dry_runNotrue = quote only: runs every check and returns price, setup fee and registrar, but creates NO pay link.
intervalNoBilling interval. Defaults to month.
site_keyYesThe site the business is paying for (must be yours, and not yet live on a domain).
price_centsNoCustom price in cents per interval. Omit for the default ($25/month). Required when the domain costs more than $20/year.
business_nameNoThe business name shown on the pay page.
contact_emailNoThe business owner's email, for your records (Stripe also collects it at payment).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) it discloses real consequences: the site comes down on cancellation or unpaid grace period, the link expires at expires_at, and creation itself is free and never charges the caller. It also decodes the failure contract — `reason`/`reason_text` values, which of them mean "not checked" versus "not sold", and the instruction not to tell the customer the ending is unsupported.

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?

Front-loads purpose and consequences before the error-code semantics, and nearly every clause carries information (payment method, currency restriction, default price, expiry, takedown condition). The sentences are long and run-on, particularly the reason/`reason_text` sentence, which could be split for faster scanning.

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?

For a 7-parameter mutation tool with no output schema, the description covers the created artifact (pay_url), billing behavior, domain gating, host-account requirement, and the error taxonomy an agent must act on. The only soft spot is that expires_at's actual value or TTL is never stated.

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 the baseline is 3, and most parameter meaning lives there. The description does add one genuinely non-schema rule — price_cents is required when the domain costs more than $20/year — plus the default $25/month framing, but it omits any explanation of how expires_at is determined or what interval/site_key interplay matters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Creates a pay link (pay_url)") and narrows the audience to business owners with no Pagetool account, plus spells out the downstream effect (domain registered, kept renewed, site live). It never names a sibling to contrast with, so an agent must infer that create_client_checkout is the opposite of cancel_client_checkout and different from purchase_link.

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?

Gives clear preconditions — signed-in accounts only, site_key must be yours and not yet live on a domain, US cards only, no existing Pagetool account — and states the quoting alternative via dry_run semantics carried in the schema. It stops short of explicit when-not guidance (e.g. "if the customer already has an account, use X instead").

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