Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Connect custom domain

custom_domain_set
DestructiveIdempotent

Connect a custom domain to a published page: a hostname the USER typed (never invent one — it must be a domain they own). Returns the CNAME record they must create at their DNS provider; SSL certificates are issued automatically after that. Then poll custom_domain_status once the user says the record is in. The subdomain URL keeps working alongside the custom domain.

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

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe pageId returned when the page was published.
hostnameYesThe domain the user typed, e.g. "get.acme.com". Apex domains work only if the DNS provider supports CNAME flattening — recommend a subdomain otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare the write/destructive/idempotent/open-world profile, but the description adds value beyond them: it discloses the return content (a CNAME record to create at the DNS provider), the automatic SSL issuance side effect, and that the subdomain URL continues to work. It does not explain reversibility or mention custom_domain_remove, which would have completed the picture.

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?

Four sentences, each carrying distinct information: action, constraint, return value, follow-up, and side effect. Front-loaded with the action and the most failure-prone constraint, with zero filler.

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?

There is no output schema, so the description carries the return-value burden and does so (CNAME record, automatic SSL). For a two-parameter mutation with a clear follow-up workflow, nothing an agent needs is missing.

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 coverage is 100%, so baseline is 3, but the description reinforces a real constraint beyond the schema: the hostname must come from the user and must be one they own. The apex-domain CNAME-flattening caveat is left entirely to the schema.

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?

States a specific verb and resource ("Connect a custom domain to a published page") plus scope, and is clearly distinguishable from siblings custom_domain_remove and custom_domain_status. An agent can pick it 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit preconditions ("a hostname the USER typed (never invent one)") and an explicit next step: "Then poll custom_domain_status once the user says the record is in." It names the follow-up sibling and the condition that triggers it.

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