Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

product

Destructive

Manage storefront merchandise by listing, retrieving, creating, updating, publishing, unpublishing, or deleting catalog entries with pricing, variations, images, SEO, and categories.

Instructions

Products of the store. Pick the operation with action and pass that action's arguments (help:true returns its full documentation and schema).

  • list_products: List products of the site (metadata only: id, name, slug, price, image, status).

  • get_product: Get full product details by ID: name, description, price, variations, images, attributes, SEO, etc.

  • create_product: Create a product so the storefront has real merchandise (grid-product / slider-product bindings need this).

  • update_product: Update an existing product.

  • delete_product: Delete one or more products by id.

  • set_product_published: Publish or unpublish one or more products quickly (without a full update).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoProduct ID [get_product]
seoNoSEO settings to change; other existing SEO tags and the slug are kept. [update_product]
skuNoSKU / custom_id for the simple case (auto-generated if omitted) [create_product]
helpNoReturn the action's full documentation and argument schema instead of running it
nameNoProduct name [create_product, update_product]
pageNoPage number [list_products]
termNoSearch by product name [list_products]
limitNoItems per page [list_products]
priceNoSelling price (used when you don't pass variations). [create_product]
stockNoStock quantity for the simple single-variation case [create_product]
actionYesWhich operation to run
imagesNoHosted image URLs (search_images/upload_images). [create_product, update_product]
attributesNoVariant axes, e.g. [create_product]
product_idNoProduct id to update [update_product]
variationsNoExplicit per-SKU variations. [create_product, update_product]
descriptionNoFull product description (HTML allowed) — binds to product::description on the detail page. [create_product, update_product]
product_idsNoProduct ids to delete [delete_product, set_product_published]
category_idsNoProduct category IDs to file the product under (from create_product_category / list_categories) [create_product, update_product]
is_publishedNoPublish/unpublish the product [update_product, set_product_published]
original_priceNoList/compare-at price for the simple single-variation case [create_product]
short_descriptionNoShort description / tagline (HTML allowed) — binds to product::short_description on cards + the d… [create_product]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds operation-level context: list returns metadata only, get returns full details, delete removes products, and publish is a lighter alternative to update. However, it does not disclose irreversibility, dependency effects, permission requirements, or what happens to related variants when deleting products, which are meaningful gaps for a destructive multi-action tool.

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 front-loaded with the action-dispatch pattern and then uses a compact bullet list where each line defines one operation. For a six-action tool with 21 parameters, the structure is efficient and every sentence contributes to operation selection.

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 tool's complexity, the description adequately enumerates every operation, explains the help:true fallback, and lets the highly descriptive schema handle argument details. It does not describe return values for create/update/delete or side effects, but the action list plus schema coverage make it sufficiently complete for selection and 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%, and the schema already tags each argument with its applicable action, including id, product_id, product_ids, help, and action-specific fields. The description mainly repeats action routing and the help flag rather than adding syntax, constraints, or interactions beyond the schema.

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 states a clear resource (store products) and enumerates six specific operations with distinct verbs and outcomes. An agent can understand that this is a multi-action product-management tool, not a category, order, or page tool, 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 Guidelines4/5

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

The description gives clear intent-based guidance for each action, such as using list_products for metadata only, get_product for full details by ID, and set_product_published to publish without a full update. It does not state explicit when-not conditions or systematically compare every action against alternatives, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.