Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

page

Destructive

Manage storefront site content via action: list, create, rename, delete, read/save source, update translations, and preview saved drafts before publishing.

Instructions

Pages of the current site: list, create, rename/SEO, delete, read and save the source, content text, preview. Pick the operation with action and pass that action's arguments (help:true returns its full documentation and schema).

  • list_pages: List all pages of the site (metadata only, without source)

  • create_page: Create a new (empty) page.

  • update_page: Update page properties: name, slug, homepage, SEO ("Cài đặt SEO") and settings.

  • delete_page: Delete a page

  • get_page_source: Get page source overview: section count, element type counts, and all custom CSS classes.

  • update_page_source: Directly update the full page source JSON.

  • list_page_contents: List multi-language contents (translations) of the site's pages and global sections.

  • update_page_content: Create/update page content for a specific language.

  • preview_page: LOOK at a saved page before publishing: screenshots of the SAVED (unpublished) draft at desktop and mobile width, through the editor's own Preview host (it renders page.source +…

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": "page"
  }
}

Input Schema

NameRequiredDescriptionDefault
seoNoSEO → settings.seo (title/description/keyword/favicon/thumbnail). [create_page, update_page]
helpNoReturn the action's full documentation and argument schema instead of running it
nameNoPage name [create_page, update_page]
slugNoURL slug WITHOUT a leading slash, e.g. [create_page, update_page]
typeNoPage kind (main/store/member/blog/custom/error/maintain). [create_page]
actionYesWhich operation to run
sourceNoFull page source object (sections tree) or JSON string [update_page_source]
widthsNoViewport widths; default desktop 1280 + mobile 420 (the site's bp1 and bp4) [preview_page]
contentNoTranslations keyed by element id → field, e.g. [update_page_content]
page_idNoPage ID [update_page, delete_page, get_page_source, update_page_source, list_page_contents, update_page_content, preview_page]
settingsNoOther page settings keys to merge (top-level keys replace) [update_page]
full_pageNoWhole scrollable page (default) or just the first screen [preview_page]
meta_tagsNoSEO meta tags [update_page_content]
native_gapNoOnly when the code was refused and no native way exists: the need, the elements/apps you checked,… [update_page_source]
custom_codeNoJS for this page only → page.settings.custom_code.code_custom_javascript (same as update_page_cus… [update_page_source]
is_homepageNoSet as homepage [create_page, update_page]
allow_shrinkNoAllow the source to shrink by more than half: set it when native elements replaced an oversized e… [update_page_source]
language_codeNoWith page_id: return just that language's content map [list_page_contents, update_page_content]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds some useful behavior: preview renders the SAVED unpublished draft through the editor's own Preview host, and update_page_source has shrink/native_gap guardrails. However, it never warns that delete_page is irreversible, that update_page_source overwrites the entire source tree, or that changes are invisible until publish — material gaps for a destructive multi-action tool.

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 layout is well front-loaded: a one-sentence scope statement, the `action`/`help` mechanism, then a tight bullet per operation. A few bullets are near-tautological (e.g. 'delete_page: Delete a page') and the tail is cut off mid-sentence, but overall length is proportionate to nine operations.

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 an 18-parameter dispatcher with nine actions and no output schema, the definition covers what each action does but not what any action returns, how source/PDF-style payloads are shaped, or where another tool (e.g. build_page, page_custom_code) should be preferred. Adequate to start, incomplete for confident use.

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% and every parameter already carries an action-scoping tag like [create_page, update_page], so the schema does most of the work. The description contributes meaning mainly at the action level rather than the parameter level, which is the expected baseline of 3.

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 states the resource (pages of the current site) and enumerates the operations with a one-line gloss each, so an agent can tell what the tool touches. It stops short of differentiating against siblings such as page_element, page_draft or build_page, which also operate on pages.

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 per-action bullet list functions as selection guidance for the `action` discriminator, and the `help:true` escape hatch tells the agent how to obtain full documentation when unsure. There are no when-not conditions and no routing to sibling tools for cases this tool does not cover.

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