Skip to main content
Glama

Update Website

hudu_update_website
Idempotent

Update an existing website monitor in Hudu to change its URL, notes, pause status, company association, or disable specific checks like DNS, SSL, and WHOIS.

Instructions

Update an existing website. A website in Hudu is a live monitor, not a documentation page: Hudu polls the host on a schedule and records its uptime, TLS certificate expiry, WHOIS registration and DNS records against the owning company.

Only the fields you supply are sent. Be aware that Hudu applies these as a PUT: for fields you do send, the new value replaces the old one outright — read the record first with hudu_get_website if you intend to append rather than overwrite.

Operation class: Update. Impact: Overwrites the supplied fields on this website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric Hudu id of the website.
nameNoThe site to monitor, written as its URL — "https://portal.contoso.com". This doubles as the display name of the record, so Hudu shows whatever you send here in lists.
notesNoFree-text notes shown on the website record, e.g. who owns the domain renewal.
pausedNotrue suspends monitoring of this host entirely — no uptime, TLS, WHOIS or DNS checks run and no alerts fire — while keeping the record and its history. This is the right setting for a planned outage or a decommissioning in progress; deleting the record throws away the history as well.
company_idNoNumeric id of the company this monitor belongs to, so its results appear on that company's page. Resolve a customer name to an id with hudu_list_companies first. The list endpoint has no company filter, so a website that is filed under the wrong company is awkward to find again.
disable_dnsNotrue stops DNS record monitoring, so Hudu no longer snapshots the domain's records or reports when they change. Uptime checking continues.
disable_sslNotrue stops TLS certificate monitoring, so Hudu no longer tracks the host's certificate or warns before it expires. Uptime checking continues. Set this for hosts served over plain HTTP or behind a certificate Hudu cannot validate, where the check would only produce noise.
disable_whoisNotrue stops WHOIS monitoring, so Hudu no longer tracks the domain registration or warns before the domain expires. Uptime checking continues. Set this for hosts on a domain the customer does not own, or on a TLD whose registry does not answer WHOIS.
Behavior4/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true), the description discloses the specific PUT semantics: only supplied fields are sent and new values replace old ones. The explicit 'Impact: Overwrites the supplied fields on this website' adds valuable behavioral context. Does not contradict annotations.

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 well-structured with a clear opening, a warning paragraph, and labeled sections (Operation class, Impact). Every sentence contributes useful information, and there is no fluff or redundancy.

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?

For a tool with no output schema, the description covers the resource model, update semantics, and key pitfalls (overwrite risk, company_id resolution). It provides enough context for an agent to use the tool correctly and safely, including appropriate helper tools.

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% with detailed parameter descriptions. The description adds the crucial 'only the fields you supply are sent' nuance and warns about overwriting, clarifying partial vs full update behavior. This is valuable beyond the schema, though most parameter meaning is already well-covered.

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 'Update an existing website' and explains what a website is in Hudu (a live monitor, not a documentation page), which distinguishes it from create/get/list siblings. The verb+resource is specific and unambiguous.

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 provides strong usage signals: it warns that only supplied fields are sent and that PUT replaces values outright, advising to read the record first with hudu_get_website when appending. It also recommends resolving company_id via hudu_list_companies. It does not explicitly contrast with all siblings, but gives clear contextual guidance.

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/ZenixSolutions/hudu-mcp'

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