Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k

update_page_element

Updates an element's style, config, events, bindings, and responsive settings, previewing changes for approval before applying.

Instructions

Update properties of a specific element in page source. Two-step process: STEP 1: Call with dry_run=true (default) → returns diff of what will change. STEP 2: Show the diff to the user and ask for confirmation. NEVER proceed without explicit user approval. STEP 3: Only after user confirms, call again with dry_run=false to apply. IMPORTANT: You MUST show the diff to the user and get explicit "yes/ok/confirm" before calling with dry_run=false. Skipping confirmation risks data loss. Merge rules: style/config/specials = shallow merge, responsive = merge by bp key. events/bindings = REPLACE the whole array — pass the COMPLETE list (read it first with get_page_element so you don't drop the others); entries are auto-normalized (id + eventName filled in, so you can pass just { action, ...fields } / { target }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoCSS style properties to merge (e.g. {color: '#fff', 'font-size': '16px'})
configNoConfig properties to merge
eventsNoComplete events array (replaces existing)
dry_runNoPreview only (true) or apply changes (false). Defaults to confirm_mode setting. Use toggle_confirm_mode to change default.
page_idYesPage ID
bindingsNoComplete bindings array (replaces existing)
specialsNoSpecials to merge (text, custom_class, custom_css, etc.)
element_idYesElement ID to update (e.g. 'TEXT-3', 'BUTTON-1')
responsiveNoResponsive breakpoint overrides (e.g. {bp1: {style: {...}, config: {...}}})
Behavior5/5

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

No annotations are provided, so the description fully carries the behavioral burden. It discloses important traits: dry_run defaults to confirm_mode setting, merge rules (shallow merge for style/config/specials, merge by bp key for responsive, REPLACE for events/bindings), auto-normalization of event/binding entries, and a warning that skipping confirmation risks data loss. This is exemplary transparency.

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 long but every sentence carries essential information. It is structured into clear steps and merge rules, making it easy to parse. No redundancy or fluff; it earns its length given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully covers the workflow (dry-run to apply), necessary prerequisites (reading get_page_element), merge behavior, and risk warnings. It also explains the default behavior of dry_run and references toggle_confirm_mode. Given the tool's complexity (9 params, nested objects, no output schema), this description is remarkably complete.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds critical semantics beyond the schema. It explains merge rules per parameter (e.g., events and bindings replace the whole array, requiring the complete list), and that entries are auto-normalized so clients can pass simplified objects. This significantly enhances understanding of parameter usage.

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's purpose: 'Update properties of a specific element in page source.' It specifies the resource (page element) and action (update), and distinguishes it from sibling tools like update_page_elements or update_page by focusing on a single element and the two-step dry-run process.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit step-by-step usage: call with dry_run=true (default), show diff, get explicit user confirmation, then call with dry_run=false. It also advises reading get_page_element first to get the complete list for events/bindings, preventing data loss. This is strong guidance on when and how to use the tool.

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/vuluu2k/webcake-storefront-mcp'

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