Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

global_section

Destructive

Manage reusable header, footer, and shared content sections: list, inspect, create, search, delete, and embed them across storefront pages.

Instructions

Global header/footer/custom sections shown on every page. Pick the operation with action and pass that action's arguments (help:true returns its full documentation and schema).

  • list_global_sections: List reusable global sections (Header, Footer, shared content blocks) — SLIM summary only.

  • get_global_section: Get one global section as a COMPACT tree (3-5x fewer tokens than raw JSON).

  • create_global_section: Create a reusable global section (Header / Footer / shared block) the way the builder does: persists a global_section record AND embeds the same section node into page sources s…

  • delete_global_section: Delete a global section (Header/Footer/block) and remove its node from every page source.

  • search_global_section_elements: Search/filter elements within a global section (Header/Footer/block) without dumping the whole tree.

  • get_global_section_element: Get full detail (style, config, specials, events, bindings, responsive bp1..bp4, children IDs) of a single element inside a global section.

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": {
      "action": "<action>"
    },
    "name": "global_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFilter by element ID substring [search_global_section_elements]
rawNoReturn the FULL raw section JSON (large) instead of the compact tree — delivered via the large-re… [get_global_section]
helpNoReturn the action's full documentation and argument schema instead of running it
nameNoDisplay name in the editor (e.g. [create_global_section]
textNoFilter by text content substring [search_global_section_elements]
typeNoheader = top chrome (logo/nav/cart), footer = bottom chrome, section = reusable content block [create_global_section, search_global_section_elements]
limitNoMax results (default 50) [search_global_section_elements]
actionYesWhich operation to run
dry_runNoPreview which pages would change (true) or perform the atomic save (false). [create_global_section, delete_global_section]
sectionNoA section node from new_section (object or JSON string) — the content of the header/footer. [create_global_section]
has_bindNoOnly elements with data bindings [search_global_section_elements]
page_idsNoPages to embed into. [create_global_section]
element_idNoElement ID (e.g. [get_global_section_element]
has_eventsNoOnly elements with events [search_global_section_elements]
section_idNoThe global section's section_id (the section node id) — from list_global_sections. [delete_global_section]
custom_classNoFilter by custom class substring [search_global_section_elements]
has_custom_classNoOnly elements with a custom class [search_global_section_elements]
global_section_idNoGlobal section ID (from list_global_sections) [get_global_section, search_global_section_elements, get_global_section_element]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description earns additional credit by disclosing the actual blast radius: create 'persists a global_section record AND embeds the same section node into page sources', delete removes the node 'from every page source'. It also documents the help:true escape hatch. It does not state permission requirements or default dry_run behavior, and the create bullet is truncated mid-sentence.

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 scope statement is front-loaded and the six actions are presented as a scannable list with a consistent verb+resource pattern. Points are lost because several bullets are visibly truncated ('into page sources s…', name/type/element_id examples cut off mid-parenthesis), which costs information for no benefit.

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 an 18-parameter, six-action polymorphic tool with no output schema, the description covers every action and points to help:true for full per-action schemas, and it distinguishes slim/compact/full return shapes. It omits default value behavior for dry_run and limit, and gives no guidance on permissions or what the compact tree looks like, which keeps it short of a 5.

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 100%, so the schema already documents all 18 parameters and even tags each with its applicable action in brackets. The description adds only the `action` dispatch concept and help:true, which the schema also covers, so the baseline 3 applies.

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 opening line states the resource and scope ('Global header/footer/custom sections shown on every page'), and each of the six actions gets a specific verb+resource bullet (list, get, create, delete, search elements, get element detail). An agent can distinguish the actions from each other without opening the schema.

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 explains the dispatch pattern ('Pick the operation with `action` and pass that action's arguments') and adds routing hints between actions, e.g. list gives a 'SLIM summary only', search works 'without dumping the whole tree', get_element returns 'full detail'. It stops short of naming when to use this tool versus siblings like page or global_source, so no explicit exclusions.

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