Skip to main content
Glama

remove_custom_domain

Release a custom domain mapping to stop routing traffic to Run402. Provide the domain and optional project ID for verification.

Instructions

Release a custom domain mapping. Traffic to the domain will no longer route to Run402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe custom domain to release (e.g. 'example.com')
project_idNoOptional project ID for ownership verification
Behavior2/5

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

With no annotations, the description carries the full burden but only mentions traffic change. Does not disclose if the domain is deleted, if it's reversible, or potential errors (e.g., domain not found). Lacks side-effect detail.

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?

Two sentences, no fluff. Front-loaded with the main action and immediate consequence. Efficient use of words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple tool, but without output schema or annotations, it would benefit from mentioning success/error outcomes or prerequisites. Misses opportunity to fully inform agent.

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% and parameter descriptions in schema are clear. Tool description adds no additional meaning beyond the schema. 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?

Clearly states the action ('release a custom domain mapping') and the effect ('traffic will no longer route to Run402'). Distinguishes from sibling like add_custom_domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like add_custom_domain or check_domain_status. Does not specify prerequisites (e.g., domain must be currently mapped).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kychee-com/run402'

If you have feedback or need assistance with the MCP directory API, please join our Discord server