Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

agency-hosting_unlinkDomainFromAgencyPlanWebsiteV1

Unlink a domain from an Agency Plan website to stop serving traffic on that domain while preserving website files and database.

Instructions

Unlinks a domain from the specified Agency Plan website.

The website stops serving traffic on this domain immediately.

Website files and database are preserved, and any other linked domains remain accessible.

If this is the only domain on the website, unlinking leaves the website without an accessible domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name
website_uidYesAgency Plan website UID
Behavior4/5

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

With no annotations, the description fully covers behavioral traits: immediate traffic stop, preservation of files/db, accessibility of other domains, and edge case of only domain. However, it does not mention reversibility, permission requirements, or any DNS changes, but overall it's informative.

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 concise sentences, each adding value. The first sentence clearly states the purpose, and subsequent sentences explain consequences. No wasted 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?

While the description covers side effects well, it lacks mention of return values (no output schema) and error conditions. For a simple unlink action, it is moderately complete but could include common failure reasons.

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% with clear parameter descriptions. The tool description adds context but no additional parameter-specific meaning beyond what the schema already provides.

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 clearly states the action ('Unlinks a domain') and the resource ('Agency Plan website'). It distinguishes from siblings like linkDomainToAgencyPlanWebsiteV1 and changeAgencyPlanWebsiteDomainV1, and explains immediate consequences.

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

Usage Guidelines3/5

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

Usage context is implied but not explicit. The description explains what happens after unlinking, but does not specify when to use this tool vs alternatives (e.g., changeDomain or deleteWebsite) nor any prerequisites like the domain being currently linked.

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/hostinger/api-mcp-server'

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