delete_domain
Remove a closed CDN domain from your account. Only domains in closed status can be deleted.
Instructions
删除已关闭的 CDN 域名
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | 要删除的域名(仅关闭状态的域名可删除) |
Remove a closed CDN domain from your account. Only domains in closed status can be deleted.
删除已关闭的 CDN 域名
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | 要删除的域名(仅关闭状态的域名可删除) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses the precondition (closed state) but does not mention irreversibility, permission requirements, or side effects. This is adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with verb and resource, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple deletion tool with one parameter, the description is mostly complete. It lacks details on return value or confirmation, but given no output schema, this is a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema fully documents the parameter. The description adds no new information beyond the schema's description, providing no additional meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('delete'), the resource ('CDN domain'), and the condition ('closed'). This distinguishes it from siblings like disable_domain or create_domain.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states the prerequisite: only closed domains can be deleted. It implies when to use (domain is closed) and when not to use (domain not closed). However, it does not mention alternative tools for non-closed domains.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yingcaihuang/racorecloud-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server