Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k

build_page

Create a WebCake storefront page with its full content source in one step. Preview via dry-run first, then save to publish.

Instructions

Create a brand-new page AND set its full content source in one step. Two-step safety: call with dry_run=true (default) to validate and preview, then dry_run=false to actually create + save. The source must be { sections: [...] } — build sections with new_section. Validation errors block the real save.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seoNoSEO for this page → settings.seo. Without it the page publishes with an EMPTY title/description. For a store page a good default title is '{{name_product}} | {{name_site}}' (product) or '{{name_category}} | {{name_site}}' (category).
nameYesPage name
slugYesURL slug WITHOUT a leading slash, e.g. 'about', 'collections', 'cart'. A leading '/' is stripped automatically (the storefront matches the bare path segment, so '/cart' would 404). Store pages MUST use the conventional slugs: category='collections', product detail='products', cart='cart', checkout='checkout', thank-you='complete'. The homepage needs no slug (pass is_homepage:true).
typeNoPage kind. SPECIAL pages need a site data-source enabled — build_page does this automatically: store→use_store (product/cart bindings), member→use_member (customer/order bindings), blog→use_blog, error→use_error, maintain→use_maintain. 'main'/'custom' need nothing. Omit for a normal content page (defaults to 'main' for the homepage).
sourceNoFull page source { sections: [...] } (object or JSON string)
dry_runNoPreview+validate only (true) or create+save (false)
is_homepageNoSet as the site homepage
Behavior4/5

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

With no annotations, the description carries the disclosure burden. It transparently explains the two-step dry_run safety mechanism, that validation errors block the save, and the required source format. It does not mention auto-enabling data sources for special page types (covered in schema), but provides strong behavioral guidance.

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 three sentences, front-loaded with the core purpose, followed by critical safety workflow and source requirement. Every sentence earns its place, with no redundant fluff.

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?

Given a complex 7-parameter tool with a rich schema but no output schema, the description covers the essential workflow and validation behavior. It does not describe return values, but the stepwise safety info and source requirements make it largely complete for an AI agent to operate effectively.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds meaning beyond the schema: it explains the dry_run validation/save sequence and directs users to build sections with new_section, clarifying the source parameter's structure and workflow. This adds practical parameter usage context.

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 'Create a brand-new page AND set its full content source in one step,' combining a specific verb and resource. It differentiates from sibling tools like create_page by emphasizing the one-step source setting and 'brand-new' versus update semantics.

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 provides clear context for when to use the tool: when creating a page with full content source in one step, with a two-step dry-run workflow. It mentions new_section as a companion tool but does not explicitly state exclusions or alternatives (e.g., use update_page for existing pages).

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