Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Disconnect custom domain

custom_domain_remove
DestructiveIdempotent

Disconnect a page's custom domain. The hostname stops serving the page immediately; the subdomain URL keeps working. Ask the user before calling it. Needed before the same hostname can be connected to another page.

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": {
      "pageId": "<pageId>"
    },
    "name": "custom_domain_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe pageId returned when the page was published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations declaring destructiveHint and idempotentHint, the description explains the concrete effect: the hostname stops serving the page immediately while the subdomain URL keeps working. It also adds an important human-in-the-loop requirement ('Ask the user before calling it'), which is exactly the kind of context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences with no wasted words. The immediate effect is front-loaded, followed by the confirmation requirement and the rationale, which is an efficient structure for a destructive operation.

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 single-parameter destructive tool with no output schema, the description covers the critical behavioral consequences, the required user confirmation, and the precondition for reuse of the hostname. Nothing an agent needs in order to call this safely is missing.

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?

The schema has 100% coverage for pageId and describes where it comes from. The description does not mention or add semantics for pageId, so with full schema coverage the baseline of 3 is appropriate.

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 ('Disconnect a page's custom domain') and clearly distinguishes the operation from siblings like custom_domain_set and custom_domain_status. An agent can immediately tell this removes an existing domain binding rather than configuring or inspecting one.

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 a clear precondition ('Needed before the same hostname can be connected to another page') and an explicit behavioral instruction ('Ask the user before calling it'). It does not explicitly name an alternative tool or when not to use this one, but the context is strong enough for safe invocation.

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

All Pageree toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources