Skip to main content
Glama

Update site

site_update
Destructive

Rename a site, change its source, or move it to another home wiki. Requires an admin of its home wiki or an organization owner; moving it also requires one of the new wiki. Renaming changes its address. Moving attaches the new home if the site doesn't read it yet, and leaves the old one attached until detached.

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": {
      "id": "<id>",
      "org": "<org>"
    },
    "name": "site_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe site's short name (its name lowercased, other characters made hyphens, e.g. deal-flow), or its client id.
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
nameNo
wikiNoThe name of the wiki to make its home.
sourceNocode:<tree>, or null to clear it.
capabilitiesNoWhat the site may do in a new home it doesn't read yet. ["read"] is read-only; ["read", "write"] is the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the destructive annotation, the description discloses important side effects: renaming changes the site's address, moving attaches the new home if needed, and the old home remains attached until detached. This adds useful operational context, though it does not discuss reversibility or failure behavior.

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 front-loaded with the main operations, followed by permission requirements and concise behavioral notes. Every sentence adds useful information, and there is no redundant or filler text.

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 destructive six-parameter mutation tool with no output schema, the description covers the core operations, permissions, and key side effects. It omits discussion of the capabilities parameter and does not describe return behavior, but those gaps are partly covered by the schema and annotations.

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 already high at 83%, but the description adds semantic mapping for several parameters: name relates to renaming and address changes, source relates to changing the source, and wiki relates to moving the home. It does not mention the capabilities parameter, but the schema documents that field well.

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 names three concrete operations — renaming, changing source, and moving to another home wiki — with a specific resource: a site. It clearly identifies the tool as a site mutation tool, though it does not explicitly contrast itself with sibling tools such as site_attach or site_detach.

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 provides meaningful usage context by stating the required permissions: admin of the site's home wiki or organization owner, plus admin of the new wiki when moving. It does not explicitly say when to choose this tool over related attach/detach tools, so it falls short of full when/when-not guidance.

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