Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

start_page_draft

Begin a resumable page draft to safely build multi-section storefront pages; cache sections first, then commit incrementally instead of sending everything at once.

Instructions

Start a page draft (no network). Build a multi-section page safely: cache each section with add_draft_section, then commit_page_draft persists it to the backend INCREMENTALLY (resumable on timeout). Use this instead of build_page for large/multi-section pages. The draft cache is DISPOSABLE (Redis on the remote server when REDIS_URL is set, in-memory otherwise; sliding ~2h TTL) — if a draft is ever lost, just re-send the sections, never a failure. ONE page per site for type main (homepage) / error / maintain, and slugs are unique per site: the draft is refused up-front with the existing page_id to edit instead. Only 'custom' pages can be created over and over.

Input Schema

NameRequiredDescriptionDefault
seoNoSEO for this page → settings.seo (applied on commit).
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: category='collections', product='products', cart='cart', checkout='checkout', thank-you='complete'. Homepage needs no slug (is_homepage:true).
typeNoPage kind. SPECIAL pages need a site data-source enabled on commit: store→use_store, member→use_member, blog→use_blog, error→use_error, maintain→use_maintain. 'main'/'custom' need nothing.
is_homepageNoSet as the site homepage on commit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only provide readOnlyHint=false. The description goes well beyond: it discloses that start makes no network call, that the draft cache is disposable (Redis or in-memory, sliding ~2h TTL), that commit is incremental and resumable on timeout, and that loss is never fatal. It also explains the up-front refusal returning an existing page_id.

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?

Front-loaded with the core purpose and the key alternative, and every sentence carries useful content. It is dense with parentheticals (Redis/in-memory, TTLs, type lists) which are informative but slightly heavy on the reading path.

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?

For a draft-orchestration tool with no output schema and detailed input schema, the description covers the full lifecycle (start → add sections → commit), failure/resumption semantics, and creation constraints. An agent has everything needed to invoke it 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 coverage is 100% and the schema already documents name, slug, type, is_homepage, and seo in detail. The description adds the cross-cutting uniqueness rule for main/error/maintain types, which the schema does not state, but otherwise does not enrich individual parameter meanings beyond the schema baseline.

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?

States a specific verb and resource ('Start a page draft') and immediately clarifies scope with '(no network)'. It explicitly distinguishes itself from siblings by naming add_draft_section, commit_page_draft, and build_page, so an agent can route without opening any schema.

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?

Gives explicit when-to-use ('Use this instead of build_page for large/multi-section pages'), the correct workflow order (cache sections with add_draft_section, then commit_page_draft), and the preconditions under which the draft is refused (one page per site for main/error/maintain, unique slugs). Nothing about selection is left 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