Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_page

Create a new empty storefront page with a unique slug and type. Use build_page for pages with content; duplicates return the existing page_id to edit.

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

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. Changed13 schema fields changedv1.34.1
    • addedInput schema / properties / seo / properties / author
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / seo / properties / canonical
      Added value: +{
+  "description": "Canonical URL",
+  "type": "string"
+}
    • addedInput schema / properties / seo / properties / hidden_meta_tags
      Added value: +{
+  "description": "Meta tag keys to hide, e.g. ['og:url']",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / seo / properties / markups
      Added value: +{
+  "description": "Structured data markups (JSON-LD). REPLACES the page's list; [] removes them.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "description": "JSON-LD as a string, without <script>",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "code"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / seo / properties / og_description
      Added value: +{
+  "description": "Defaults to description",
+  "type": "string"
+}
    • addedInput schema / properties / seo / properties / og_site_name
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / seo / properties / og_title
      Added value: +{
+  "description": "Defaults to title",
+  "type": "string"
+}
    • addedInput schema / properties / seo / properties / og_type
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / seo / properties / og_url
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / seo / properties / robots
      Added value: +{
+  "description": "Robots meta, e.g. \"noindex, nofollow\" or \"max-snippet:-1, max-image-preview:large\"",
+  "type": "string"
+}
    • addedInput schema / properties / seo / properties / site_name_markup
      Added value: +{
+  "description": "Emit the site-name markup (default on)",
+  "type": "boolean"
+}
    • addedInput schema / properties / seo / properties / thumbnail / description
      Added value: +"Share image; also og:image"
    • addedInput schema / properties / seo / properties / thumbnail_alt
      Added value: +{
+  "type": "string"
+}
  2. 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."
  3. First observedv1.31.8

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare this is a write (readOnlyHint=false) and non-destructive, so the safety profile is covered. The description goes further by disclosing the duplicate-slug refusal behavior and that the error surfaces the existing page_id, plus the side effect of publishing with an empty title unless seo is passed. It stops short of describing permissions or the success return payload.

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?

Purpose and the build_page alternative are front-loaded, followed by constraints. Information-dense and mostly waste-free, though the parenthetical re-listing of the type enum slightly duplicates the schema and the final sentence is packed with three separate rules.

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?

For a 5-param mutation tool with no output schema, the description covers the routing decision, the uniqueness constraints, and the empty-title pitfall. Missing only auth/permission requirements and the shape of the success response, which an agent could reasonably want.

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% so the baseline is 3, but the description adds real meaning beyond it: type is a KIND mapped to a numeric backend type, the slug uniqueness/one-per-site rules that govern valid values, and the consequence of omitting seo. That is genuine semantic enrichment, not repetition.

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+resource ('Create a new (empty) page') and immediately scopes it against the sibling build_page for pages with content. The agent can distinguish it from other page tools without opening the 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?

Explicitly names the alternative tool and the condition that selects it ('For a page with content use build_page instead'), plus hard constraints: one page per site for main/error/maintain, unique slugs per site, and only 'custom' repeatable. This is when/when-not/alternatives in full.

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