Skip to main content
Glama

Update Footer

update_footer
DestructiveIdempotent

Update the site footer — layout, social links, tagline, background colour.

Annotations: read-only=false, destructive=true, idempotent=true, open-world=false. Why: Overwrites the draft's footer content — non-additive, so destructive by the MCP definition; idempotent; closed-world. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

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_footer"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes
taglineNoFooter tagline or description
variantNo
backgroundNoFooter background — "default" (the page colour) | "alt" (soft) | "primary" (the brand colour) | "dark" (dark surface). Null clears it (the classic brand-coloured footer). Choosing a preset also clears any custom colour.
social_linksNo
background_colorNoCustom footer colour as a 6-character hex; overrides the preset. Null clears it. Text adapts automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, readOnly=false, and openWorld=false, but the description adds critical scope: it overwrites draft footer content and live changes only happen after publish_site. This explains what is destroyed and confines destructive impact to the draft, though it does not clarify whether omitted fields are preserved or cleared.

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?

The purpose is front-loaded in one sentence, followed by a concise rationale. The rationale repeats annotation booleans before explaining them, which is slightly redundant, but overall the text is efficient and well structured.

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?

The description covers mutation risk and the publish workflow, but for a six-parameter destructive update with no output schema it leaves key operational gaps: required site_id, whether omitted fields are preserved or cleared, and the interaction between preset and custom background colours. It is adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema description coverage, the description only names some fields and adds no semantics for required site_id, variant choices, social_links format, or the relationship between background and background_color. The schema carries most parameter meaning, and the description does not compensate for the coverage gap.

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?

States the verb 'update' and resource 'site footer', then enumerates layout, social links, tagline, and background colour. It is clearly distinct from update_header by resource, but it does not explicitly name alternatives or contrast with update_design, so it falls short of a 5.

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?

There is no explicit when/when-not guidance or named alternative tool. It does provide relevant publish-workflow context (live changes only after publish_site, draft remains editable), which implies usage but does not tell an agent when to choose this over update_design or update_header.

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.