Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_page

Create a new empty page by providing a name, unique slug, and type (main, store, member, blog, custom, error, maintain). Optionally set SEO metadata or mark as homepage. Duplicate slugs are rejected.

Instructions

Create a new (empty) page. For a page with content use build_page instead. type is a KIND (main/store/member/blog/custom/error/maintain) mapped to the numeric backend type; pass seo so it doesn't publish with an empty title. ONE page per site for main (homepage) / error / maintain, and slugs are unique per site — a duplicate is refused with the existing page_id to edit instead; only 'custom' pages can be created over and over.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seoNoSEO → settings.seo (title/description/keyword/favicon/thumbnail). Tokens {{name_page}}/{{name_site}} allowed.
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). Homepage needs no slug (pass is_homepage:true).
typeNoPage kind (main/store/member/blog/custom/error/maintain). store/member/blog need their data-source flag enabled — prefer build_page which auto-enables it. main/error/maintain are one-per-site; use 'custom' for extra pages.
is_homepageNoSet as homepage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.31.9
    • changedInput schema / properties / type / description
      Previous value: -"Page kind (main/store/member/blog/custom/error/maintain). store/member/blog need their data-source flag enabled — prefer build_page which auto-enables it."New value: +"Page kind (main/store/member/blog/custom/error/maintain). store/member/blog need their data-source flag enabled — prefer build_page which auto-enables it. main/error/maintain are one-per-site; use 'custom' for extra pages."
  2. First observedv1.31.8

TDQS

A4.6/5.0
Behavior4/5

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

The description discloses important behaviors: one-per-site restrictions for main/error/maintain, unique slug enforcement with duplicate refusal returning existing page_id, and automatic stripping of leading slashes. It does not mention the response format, but the key side effects and constraints are covered.

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 description is dense but packed with essential information. It is not overly verbose, though the mix of constraints, tips, and type clarifications in a few sentences makes it slightly demanding to parse. Still, every sentence adds value.

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 the schema covers all parameters and the description explains constraints and alternative tools, the description is largely complete. The lack of an output schema is not a major gap for a create operation, though mentioning the returned object would be slightly more 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?

All five parameters are described in the schema, including the slug format with examples, the type enum with special notes, SEO subfields, and is_homepage default. The descriptions add meaningful context beyond the raw types.

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 creates a new empty page and explicitly contrasts with build_page for content-bearing pages. The scope is unambiguous and distinguishes this from sibling tools.

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?

It provides concrete guidance: use build_page for content, pass seo to avoid publishing with an empty title, and clarifies page-type constraints. This tells the agent exactly when and how to use the tool versus alternatives.

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