Skip to main content
Glama

Change business details or web address

update_site
DestructiveIdempotent

Changes the business details used across the site (name, phone, email, hours, services, location, about) and, optionally, the free web address. Only the fields you pass change; pass an empty string to remove an optional detail. A published site's old address redirects to the new one for 30 days. Business detail changes appear on the live site after publish_site.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>"
    },
    "name": "update_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoNew web address before .mywebdesk.app.
briefNo
site_idYesThe site id from list_sites or create_site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, openWorldHint=true), the description discloses three behaviors the annotations cannot convey: partial-update merge semantics, that an empty string deletes an optional detail (the concrete form of the destructive flag), and that a published site's old address redirects for 30 days. It also clarifies that edits are staged and only surface after publish_site, so the agent knows the live site is not immediately affected.

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?

Three tight sentences: purpose first, then the update/removal rule, then publication and redirect consequences. Every sentence carries information an agent would otherwise have to guess, and nothing is repeated from the schema verbatim without adding meaning.

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

Completeness4/5

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

For a mutation tool with a nested brief object, no output schema and no annotation detail on side effects, the description covers intent, partial-update behavior, deletion semantics, redirect retention and the publish dependency. Remaining gaps are minor: what the call returns, whether slug changes are validated or gated, and any effect on existing links beyond the 30-day window.

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?

The description maps onto the main branches of the schema: the slug is framed as the free web address, and the brief fields are enumerated in plain language. It adds genuinely non-obvious semantics the schema does not state, namely that omitted fields are left untouched and empty strings clear optional details. It does not cover the Lead Autopilot-only fields (reviewUrl, autoReplyMessage) or businessType, so coverage remains partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: it changes the business details used across the whole site, enumerating concrete fields (name, phone, email, hours, services, location, about) and optionally the free web address. The phrase 'used across the site' implicitly separates it from page- or section-level tools like update_page or update_section, but no sibling is named explicitly.

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?

It sets clear operating context: only fields you pass change, and an empty string removes an optional detail, which is the guidance an agent needs for a partial-update tool. It also states that detail changes only reach the live site after publish_site, tying it to a neighboring tool. It stops short of saying when to prefer this over update_page/update_lead or any preconditions such as slug uniqueness.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources