Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_global_source_elements

Read-only

Search and filter elements within a WebCake global source by ID, text, type, bindings, events, or custom classes to locate storefront components for editing or validation.

Instructions

Search/filter elements within a global source. No component param needed. Examples:

  • Find all buttons: type="button"

  • Find by class: custom_class="hero"

  • Find text: text="subscribe"

  • Data-bound only: has_bind=true

  • With events: has_events=true

  • With custom class: has_custom_class=true

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": {
      "global_source_id": "<global_source_id>"
    },
    "name": "search_global_source_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFilter by element ID substring (e.g. 'TEXT', 'BUTTON-3')
textNoFilter by text content substring
typeNoFilter by element type (e.g. 'text', 'button', 'image', 'container', 'section')
limitNoMax results (default 50)
has_bindNoOnly elements with data bindings
componentNoComponent hint for faster lookup (e.g. "popup", "cart-droppable")
has_eventsNoOnly elements with events
custom_classNoFilter by custom class substring
global_source_idYesGlobal source ID
has_custom_classNoOnly elements with custom class

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only the assertion that no component parameter is required, which is mildly useful context, but says nothing about result limits (the 50 default), pagination, or the shape of the returned element set for a tool with 10 parameters.

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 sentence is front-loaded and the examples are scannable. The bullet list is slightly redundant with the schema descriptions, but each bullet maps a filter to a concrete use case rather than padding.

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?

For a 10-parameter read tool with no output schema, the description covers filter usage adequately but omits the default result cap, pagination behavior, and any routing against the many neighboring element-search tools. Adequate but with clear gaps.

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 baseline is 3. The examples add concrete sample values for the filter parameters (type="button", custom_class="hero", text="subscribe"), which is modest added value, but the semantics of each flag are already fully stated in the schema.

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 a specific verb and resource: search/filter elements within a global source. It is distinguishable from the similarly named search_global_section_elements and get_global_source_element by the 'within a global source' scope, though it never names those siblings explicitly. The odd 'No component param needed' line slightly muddies the scope since the schema does expose a component parameter.

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?

The six examples effectively demonstrate when each filter is useful (buttons, classes, text, bindings, events), which is better than nothing. However, there is no statement of when NOT to use this tool or which sibling to prefer for a single-element lookup or section-scoped search, leaving the routing decision to inference.

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

Deploy Server

Other Tools