Skip to main content
Glama

Pagetool

Create a one-time site transfer link

create_transfer_code

Creates a one-time link that hands a managed site to a departing client: they sign in or sign up and accept, and the site (and, by default, its domain) moves to their account. The link works once and expires at expires_at; creating a new one cancels the previous one. Signed-in accounts only.

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>"
    },
    "name": "create_transfer_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_keyYesThe managed site to hand over to a departing client.
include_domainNoMove the site's connected domain with it (default true). When false the site moves unpublished and the domain stays with this account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description carries substantial behavior beyond the annotations: single-use semantics, expiry, that creating a new link cancels the previous one, and that the caller must be signed in. These are exactly the side effects and preconditions an agent needs (the cancellation behavior in particular is not conveyed by destructiveHint=false), so this adds real value over the structured fields.

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?

Two sentences with the core action front-loaded and no filler; the recipient flow and constraints are packed efficiently. The dangling 'expires_at' reference is the one piece of wording that does not earn its place, since it points at a nonexistent field.

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 two-parameter mutation with no output schema, the description covers preconditions (signed-in), lifecycle (single use, expiry, cancellation of prior links), and the effect on the domain. The only remaining ambiguity is what the call returns (presumably the link itself), which is minor given there is no output schema to explain it.

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 the baseline is 3; the description only loosely reinforces include_domain with 'by default, its domain.' It also references 'expires_at' as if it were an input, but no such parameter exists in the schema, which weakens rather than strengthens parameter guidance.

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 a specific verb and resource ('Creates a one-time link') and states the exact outcome: a managed site, plus by default its domain, moves to a departing client's account. This is distinct from siblings like export_site_html or archive_site, which do not transfer ownership, so an agent can identify the right tool without opening the schema.

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 clearly establishes the scenario ('hands a managed site to a departing client') and the recipient flow ('they sign in or sign up and accept'), plus the constraint of signed-in accounts only. It does not explicitly exclude alternatives such as exporting or archiving a site for a departing client, so the boundary with siblings is implied rather than stated.

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