Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_page

Modify a storefront page's name, slug, homepage status, SEO, and settings; fields not provided remain unchanged.

Instructions

Update page properties: name, slug, homepage, SEO ("Cài đặt SEO") and settings. seo / settings are MERGED into the page's current settings — fields you don't pass are kept.

Input Schema

NameRequiredDescriptionDefault
seoNoSEO → settings.seo (title/description/keyword/favicon/thumbnail/og_*). Merged; other SEO fields kept. Tokens {{name_page}}/{{name_site}} allowed.
nameNoNew name
slugNoNew slug WITHOUT a leading slash (e.g. 'about', 'cart'). A leading '/' is stripped automatically — '/cart' would 404 on the storefront.
page_idYesPage ID
settingsNoOther page settings keys to merge (top-level keys replace)
is_homepageNoSet as homepage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.34.1
    • addedInput schema / properties / seo
      Added value: +{
+  "additionalProperties": false,
+  "description": "SEO → settings.seo (title/description/keyword/favicon/thumbnail/og_*). Merged; other SEO fields kept. Tokens {{name_page}}/{{name_site}} allowed.",
+  "properties": {
+    "author": {
+      "type": "string"
+    },
+    "canonical": {
+      "description": "Canonical URL",
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "favicon": {
+      "type": "string"
+    },
+    "hidden_meta_tags": {
+      "description": "Meta tag keys to hide, e.g. ['og:url']",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "keyword": {
+      "type": "string"
+    },
+    "markups": {
+      "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"
+    },
+    "og_description": {
+      "description": "Defaults to description",
+      "type": "string"
+    },
+    "og_site_name": {
+      "type": "string"
+    },
+    "og_title": {
+      "description": "Defaults to title",
+      "type": "string"
+    },
+    "og_type": {
+      "type": "string"
+    },
+    "og_url": {
+      "type": "string"
+    },
+    "robots": {
+      "description": "Robots meta, e.g. \"noindex, nofollow\" or \"max-snippet:-1, max-image-preview:large\"",
+      "type": "string"
+    },
+    "site_name_markup": {
+      "description": "Emit the site-name markup (default on)",
+      "type": "boolean"
+    },
+    "thumbnail": {
+      "description": "Share image; also og:image",
+      "type": "string"
+    },
+    "thumbnail_alt": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / properties / settings / description
      Previous value: -"Page settings"New value: +"Other page settings keys to merge (top-level keys replace)"
  2. First observedv1.31.8

TDQS

A3.9/5.0
Behavior4/5

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

Annotations supply only readOnlyHint=false, so the description carries real weight here. It discloses the non-obvious merge semantics for 'seo' and 'settings' ('fields you don't pass are kept'), which is exactly the kind of partial-update behavior an agent must know to avoid clobbering data. It omits the counter-case documented in the schema (markups REPLACES the page's list, [] removes them) and says nothing about permissions or the failure mode of an invalid slug.

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?

Two sentences, zero filler, and the payload ('Update page properties: ...') is front-loaded ahead of the merge caveat. The Vietnamese UI label '(\"Cài đặt SEO\")' is directly actionable for an agent navigating admin strings.

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?

Mutation tool with one required param, nested SEO/settings objects, no output schema and minimal annotations. The description covers the essential non-obvious risk (merge vs replace at the top level), the schema covers per-field detail including slug and markups semantics, and annotations flag it as a write. Adequate for correct invocation.

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%, including the slug formatting and the markups-replaces rule, so the schema already documents every parameter in detail. The description restates the parameter set and the merge behavior but adds no format, constraint or example information beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb and resource ('Update page properties') and enumerates the affected fields (name, slug, homepage/hompage flag, SEO, settings), which separates it in practice from siblings like update_page_content, update_page_source and update_page_element. It never names a sibling explicitly, so differentiation must be inferred from the field list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The field enumeration implies 'use this for page metadata/settings, not page content or source', but there is no explicit when-to-use statement, no reference to the overlapping siblings (update_page_content, update_page_source, update_page_elements), and no prerequisites (e.g. a draft must exist first). Usage is only implied.

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