Page Lemon

Transfer site

transfer_site

Destructive

Offers a site to a new Site Owner by email, who accepts and picks where it lives. Returns approve_url and recipient (what the site needs beyond Free, the same for any address); the sender's bill doesn't change. keep_editor (default true): the sender stays Site Developer. A workspace site goes to its Site Owner or someone in it.

Input Schema

Name	Required	Description
`site`	Yes
`email`	No	The new Site Owner's email (required unless confirm_token)
`keep_editor`	No
`confirm_token`	No

Output Schema

Name	Required	Description	Default
`recipient`	No
`approve_url`	No
`agent_message`	No
`confirm_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 27, 2026
- addedOutput schema / properties / agent_message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / approve_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recipient
```
Added value: +{
+  "type": "object"
+}
```

Changed2 schema fields changedOct 25, 2026

removedInput schema / properties / confirm_token / description
```
Removed value: -"From the first call: approval status"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "confirm_token": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 22, 2026
- removedInput schema / properties / site / description
```
Removed value: -"Site name"
```

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / confirm_token / description

Previous value: -"From the first call: re-call with it for the approval status"New value: +"From the first call: approval status"

changedInput schema / properties / site / description

Previous value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "agent_message": {
-      "type": "string"
-    },
-    "confirm_token": {
-      "type": "string"
-    },
-    "error": {
-      "description": "On failure (isError): {code, message}"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed2 schema fields changedOct 15, 2026

removedInput schema / properties / cancel

Removed value: -{
-  "description": "true: cancel the pending transfer",
-  "type": "boolean"
-}

changedInput schema / properties / email / description

Previous value: -"The new Site Owner's email"New value: +"The new Site Owner's email (required unless confirm_token)"

Changed2 schema fields changedOct 14, 2026

changedInput schema / properties / email / description

Previous value: -"The new owner's email"New value: +"The new Site Owner's email"

removedInput schema / properties / workspace

Removed value: -{
-  "description": "Instead of an email: move the site into this workspace (id or name, see get_account), \"personal\" (out of a workspace into your own account), or \"new\" (creates a workspace the user then pays for in the app)",
-  "type": "string"
-}

First observedOct 14, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond annotations that already flag destruction, open-world behavior, and non-idempotency, the description discloses the invitation/acceptance workflow, return fields, unchanged billing for the sender, the keep_editor default, and workspace eligibility constraints. These are meaningful behavioral details an agent would not get from annotations alone.

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 description is compact and front-loads the core action and workflow before details. The parenthetical about what the site needs beyond Free is slightly dense, but every sentence contributes relevant information.

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?

With an output schema and annotations covering safety and return behavior, the description supplies the operational context an agent needs for the main flow. The remaining gap is confirm_token's conditional purpose, which is not explained even though the schema makes it relevant when email is omitted.

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 only 25%, so the description must compensate. It usefully explains keep_editor's default and effect, and implies email's role, but it leaves the site parameter and especially confirm_token unexplained, so the coverage gap is only partly filled.

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 states a specific verb and resource — offering a site to a new Site Owner by email — plus the acceptance flow where the recipient chooses where the site lives. This clearly separates it from immediate operations like move_sites and is understandable 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 gives clear usage context: the site is offered to a new owner who must accept, and workspace sites can only go to the Site Owner or someone in the workspace. It does not explicitly name alternatives such as move_sites or cancel_transfer, so it stops short of full when/when-not guidance.

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

All Page Lemon tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?