Skip to main content
Glama

Update website

update_website
Destructive

Update the guide's public website settings: theme, layout, colors, hero image, description, location, website link, or contact phones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNo
locationNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
descriptionNo
site_layoutNo
website_urlNo
hero_data_urlNoA base64 data URL for the hero image.
contact_phonesNo
site_accent_colorNo
site_primary_colorNo
site_show_languagesNo
site_background_colorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is covered. However, the description adds no behavioral context of its own: it does not say that changes go live on a public site immediately, whether omitted fields are left untouched, what happens to previously set values, or how the base64 hero image affects payload limits. For a destructive, open-world mutation the field list alone is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every listed facet corresponds to a real parameter. The enumeration gets long but each item earns its place by naming a capability the agent would otherwise have to infer from a 17%-documented schema.

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

Completeness2/5

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

For a 12-parameter destructive mutation with no output schema and very sparse schema descriptions, the definition leaves major gaps: partial-update semantics, color value format, base64 payload expectations, and the effect on the live public site are all unaddressed. An agent could call it, but would be guessing on several material points.

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 description coverage is only 17%, so the description should compensate, and it does partially by mapping human-readable labels to most parameters (theme, layout, three colors, hero image, description, location, website link, contact phones). It omits business_id and site_show_languages entirely and gives no format guidance (hex vs named colors, accepted URL scheme, phone object shape), so it improves discoverability without delivering real semantics.

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 gives a specific verb ('Update') plus a concrete resource ('the guide's public website settings') and enumerates the mutable facets (theme, layout, colors, hero image, description, location, link, phones). That is enough to tell it apart from get_website/import_website by verb alone, though no sibling is named.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus get_website or import_website, and no prerequisites (e.g., required permissions or that the business must already exist). The word 'Update' implies usage but nothing is explicit, and the critical fact that all 12 parameters are optional (partial update) is never mentioned.

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