Skip to main content
Glama

Vee3

by io.github.Vee3io

pages.set_custom_domain

Attach a custom hostname to a hosted static website.

The hostname must be on a domain this Vee3 account already manages. Vee3 writes DNS and attaches the hostname to the page CDN with TLS. Subdomains use CNAME; the domain apex uses ALIAS. The preview hostname on vee3.site stays available. Setting a new custom domain replaces the previous one. If HTTPS is not ready yet, call this tool again after DNS is live; Vee3 retries TLS issuance.

Cost = 50 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesPage id to attach the custom domain to.
custom_domainYesHostname to attach, such as www.example.com or example.com. Must be on a domain this Vee3 account already manages. At most 253 characters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic HTTPS URL for the page. Uses the custom domain when one is attached.
nameNoDisplay name for the page, if set.
slugNoPage slug.
statusNoCurrent page status.
messageNoNote that DNS and TLS can take several minutes to become available, and sometimes up to about 30 minutes.
page_idNoUnique identifier for the page.
hostnameNoPreview hostname ({slug}.vee3.site). Always present, including when a custom domain is attached.
created_atNoWhen the page was created.
updated_atNoWhen the page record was last updated.
custom_domainNoCustom hostname attached to the page, if any.
last_deployed_atNoWhen files were last deployed to the page.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses side effects (Vee3 writes DNS, attaches CDN with TLS), technical details (CNAME for subdomains, ALIAS for apex), replacement behavior, preview hostname persistence, and TLS retry behavior. The cost field adds practical operational transparency.

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 compact and front-loaded with the primary purpose. Every subsequent sentence adds distinct behavioral value: prerequisites, DNS mechanics, replacement semantics, retry guidance, and cost. There is no redundancy or 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?

Given the tool's moderate complexity and lack of annotations, the description covers prerequisites, side effects, retry behavior, and replacement semantics. An output schema exists, so return values do not need explanation. Nothing an agent needs to call it safely and correctly 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?

Schema description coverage is 100%, so the schema already documents both parameters and the managed-domain constraint. The description adds behavioral nuance like CNAME vs. ALIAS, but that is not needed to understand parameter meaning; it stays at the baseline without adding significant param-level semantics.

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 opens with a specific verb and resource: 'Attach a custom hostname to a hosted static website.' It clearly distinguishes this from close siblings like pages.remove_custom_domain and domains.add_dns_host by scoping it to attaching a hostname with DNS, CDN, and TLS handled by Vee3.

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?

The description gives a clear context: only use for domains the Vee3 account already manages, and provides a retry instruction when HTTPS is not ready. It does not explicitly name alternative tools or state exclusions, but the usage context is unambiguous enough for an agent to route correctly.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources