Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_article

Update a blog article by changing only the fields you provide—title, slug, tags, images, content, summary, visibility, categories, or publish date. Pass a custom slug when renaming to keep the URL.

Instructions

Update a blog article. Only the fields you pass are changed — each one becomes a command in the same dashboard pipeline create_article uses. NOTE: renaming regenerates the slug, so pass slug in the SAME call if you want a custom one (it is applied after the rename).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesArticle ID
nameNoNew title (regenerates the slug unless slug is also passed)
slugNoNew custom slug
tagsNoArticle TAG IDs (uuids from the blog tag list) — not free text
imagesNoHosted image URLs; the first is the cover image
contentNoNew HTML content (replaces the old content)
summaryNoNew summary / excerpt
is_hiddenNoHide from public
category_idsNoBlog category IDs to file the post under (added, existing ones are kept)
published_atNoPublish date, ISO/naive datetime (render_inserted_at)
remove_category_idsNoBlog category IDs to unfile the post from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.31.10
    • removedInput schema / properties / category_id
      Removed value: -{
-  "description": "Category ID",
-  "type": "string"
-}
    • addedInput schema / properties / category_ids
      Added value: +{
+  "description": "Blog category IDs to file the post under (added, existing ones are kept)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / content / description
      Previous value: -"New HTML content"New value: +"New HTML content (replaces the old content)"
    • addedInput schema / properties / images
      Added value: +{
+  "description": "Hosted image URLs; the first is the cover image",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / name / description
      Previous value: -"New title"New value: +"New title (regenerates the slug unless slug is also passed)"
    • addedInput schema / properties / published_at
      Added value: +{
+  "description": "Publish date, ISO/naive datetime (render_inserted_at)",
+  "type": "string"
+}
    • addedInput schema / properties / remove_category_ids
      Added value: +{
+  "description": "Blog category IDs to unfile the post from",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"New slug"New value: +"New custom slug"
    • changedInput schema / properties / summary / description
      Previous value: -"New summary"New value: +"New summary / excerpt"
    • changedInput schema / properties / tags / description
      Previous value: -"Tags"New value: +"Article TAG IDs (uuids from the blog tag list) — not free text"
  2. First observedv1.31.8

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the partial-update behavior ('only the fields you pass are changed'), the fact that each field becomes a command in the same pipeline as create_article, and the critical slug regeneration interaction (renaming regenerates slug; pass slug in the same call and it's applied after the rename). This is valuable behavioral detail beyond the schema. It doesn't cover auth, reversibility, or response format, but the provided details are substantial.

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 compact: two sentences with no filler. The main purpose is stated first, followed by the key behavioral caveat about slug handling. Every clause earns its place, and it's front-loaded with the most important information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 11 parameters and no output schema, the description provides the critical slug caveat but omits other context an agent might need, such as what the response returns, any authentication requirements, or side effects beyond the slug change. The schema covers parameter definitions well, but the description doesn't fully compensate for the lack of annotations or output schema. It's adequate but not exhaustive.

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%, so the baseline is 3. The description adds one meaningful semantic detail: the ordering of slug application relative to rename, which is not fully in the schema (the schema mentions regeneration but not the order). For other parameters, the description adds nothing beyond the schema. Thus it slightly exceeds baseline, but not enough for a 4.

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?

The description clearly states 'Update a blog article' with a specific verb and resource. It also notes that only passed fields change, and references the same pipeline as create_article, which hints at a relationship to siblings. However, it doesn't explicitly differentiate from other article tools (e.g., delete_article) or from create_article beyond the verb, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when not to use it, or that it's for existing articles only. The reference to create_article's pipeline is vague and doesn't help an agent choose between them. The slug note is behavioral, not usage selection.

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