Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

global_source

Destructive

Manage site-wide storefront sources such as popups, cart drawers, headers, and footers. List, inspect, create, edit, search, and translate their components through one action-based tool.

Instructions

Site-wide sources (popups, cart drawer, header/footer sources): list, read, create, edit, translate. Pick the operation with action and pass that action's arguments (help:true returns its full documentation and schema).

  • list_global_sources: List global sources (cart, popup, etc.).

  • get_global_source_detail: Get full detail of a global source — compact tree view showing all elements.

  • create_global_source: Create a new global source component.

  • update_global_source: Replace full source of a global source.

  • delete_global_source: Delete a global source and its published version

  • search_global_source_elements: Search/filter elements within a global source.

  • get_global_source_element: Get full detail of a single element (style, config, specials, events, bindings, responsive, children).

  • update_global_source_element: Update a single element within a global source.

  • update_global_source_elements: Batch update multiple elements in one global source.

  • get_global_source_contents: Get multilingual contents for global sources by component type

  • update_global_source_contents: Update multilingual contents (upsert).

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

Input Schema

NameRequiredDescriptionDefault
idNoFilter by element ID substring (e.g. [search_global_source_elements]
helpNoReturn the action's full documentation and argument schema instead of running it
textNoFilter by text content substring [search_global_source_elements]
typeNoType variant (default: "default") [create_global_source, search_global_source_elements]
limitNoMax results (default 50) [search_global_source_elements]
styleNoStyle to merge, camelCase like the editor (e.g. [update_global_source_element]
actionYesWhich operation to run
configNoConfig to merge (layout: widthUnit auto|px|%, constraintX/Y, columnStart…). [update_global_source_element]
eventsNoComplete events array (replaces existing) [update_global_source_element]
sourceNoSource configuration (sections/elements JSON) [create_global_source, update_global_source]
dry_runNoPreview only (true) or apply changes (false). [update_global_source_element, update_global_source_elements]
updatesNoArray of element updates [update_global_source_elements]
bindingsNoComplete bindings array (replaces existing) [update_global_source_element]
contentsNoArray of content entries to upsert [update_global_source_contents]
has_bindNoOnly elements with data bindings [search_global_source_elements]
specialsNoSpecials to merge (text, custom_class, custom_css) [update_global_source_element]
componentNoFilter by component type (e.g. [list_global_sources, get_global_source_detail, create_global_source, search_global_source_elements, get_global_source_element, update_global_source_element, update_global_source_elements, get_global_source_contents]
element_idNoElement ID (e.g. [get_global_source_element, update_global_source_element]
has_eventsNoOnly elements with events [search_global_source_elements]
responsiveNoResponsive overrides (e.g. [update_global_source_element]
allow_shrinkNoAllow the source to shrink by more than half: set it when native elements replaced an oversized e… [update_global_source, update_global_source_element, update_global_source_elements]
custom_classNoFilter by custom class substring [search_global_source_elements]
global_source_idNoGlobal source ID [get_global_source_detail, update_global_source, delete_global_source, search_global_source_elements, get_global_source_element, update_global_source_element, update_global_source_elements]
has_custom_classNoOnly elements with custom class [search_global_source_elements]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds useful specifics: delete removes the source and its published version, update replaces the full source, and contents updates are upserts. It also mentions batch updates and dry-run previews via the schema. It does not describe permission requirements, reversibility, or rate limits.

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 scope and dispatch mechanism, followed by a terse action list that maps directly to the enum. Each bullet is short and informative, and the `help:true` note is useful without being verbose. There is no significant wasted wording.

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 complex dispatcher with 11 actions and 24 parameters, the description enumerates every action and supports runtime discovery via `help:true`. Because there is no output schema, return-value explanation is limited to short action hints such as compact tree view or full detail, but the action list is otherwise complete enough to call the tool correctly.

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 the 24 parameters, including action applicability and defaults. The description explains the action dispatch model but adds little parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the resource and scope: site-wide sources such as popups, cart drawer, and header/footer sources, with list/read/create/edit/translate operations. It then enumerates all supported actions, making the tool's overall purpose easy to understand. It does not explicitly distinguish itself from similar siblings such as global_section or page_element.

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 gives clear context for when the tool applies: site-wide sources such as cart, popup, header/footer, and multilingual contents. It also explains how to select an operation using `action` and points to `help:true` for per-action documentation. It lacks explicit when-not guidance or named alternatives among sibling tools.

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