Skip to main content
Glama

thincms_update_navigation

Update header and/or footer navigation by fully replacing the item array. Each item can be a page slug, a CMS route path, or an external URL. Max 20 items per nav.

Instructions

Update header and/or footer navigation. Each is a full replacement array (max 20 items). Item types: 'page' (target = page slug, must exist and be published), 'route' (target = CMS path like /blog or /search), 'external' (target = full URL).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdNoOverride the active site for this single call. Pass to target a specific tenant without mutating shared active-site state — the right pattern when running concurrent agent sessions managing different tenants. Must match a siteId from your THINCMS_SITES config (use thincms_list_sites to inspect). When omitted, the call uses the active site set by thincms_switch_site.
footerNavNoFooter navigation items
headerNavNoHeader navigation items
confirmProductionWriteNoAcknowledge that this call may write to a configured production site (THINCMS_PRODUCTION_SITE_IDS env var). Required for any POST/PUT/PATCH/DELETE against a production-listed site; ignored otherwise. The error message lists which site triggered the requirement and recommends thincms_snapshot before any production write.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the full replacement behavior (implying destructiveness) and constraints on item types, but it does not mention side effects, authentication needs, rate limits, or what happens to existing navigation items. The description adds value but could be more explicit about behavioral traits.

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 concise: two sentences that front-load the core purpose and immediately clarify key constraints (full replacement, max 20 items, item types). Every sentence adds value with no wasted words, and the structure is easy to parse.

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?

The description covers the essential aspects: what it does, the replacement nature, item types, and limits. It does not mention the siteId or confirmProductionWrite parameters, but those are well-described in the schema with 100% coverage. No output schema is needed since the operation's success is typically indicated by a status code. Overall, it is sufficiently complete for its purpose.

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%, but the description adds meaning beyond the schema by clarifying item types (e.g., 'page' requires a published slug, 'route' expects a CMS path) and providing examples. This helps the agent understand the valid values and constraints, enhancing usability beyond the raw schema descriptions.

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 the tool updates header and/or footer navigation, specifying it is a full replacement array with a maximum of 20 items. It distinguishes itself from siblings like thincms_get_navigation by explicitly describing the update action and the constraints on item types, making the purpose 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 implies when to use (to update navigation) and the nature of the operation (full replacement), but it does not explicitly state when not to use this tool or list alternatives such as thincms_get_navigation for reading. However, the context provided is sufficient for an agent to infer appropriate usage.

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/pmccarroll-fuel/thincms-mcp'

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