Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

product_category

Destructive

Manage storefront product categories by listing, creating, updating, or deleting them so products can be organized and category pages populated.

Instructions

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

  • list_categories: List all product categories of the site

  • create_product_category: Create a product category (so grid-category / a category page has something to show, and products can be filed under it).

  • update_product_category: Update a product category (name, image, description, visibility, SEO).

  • delete_product_category: Delete one or more product categories by id.

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_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoCategory id [update_product_category]
idsNoCategory ids to delete [delete_product_category]
seoNoSEO settings to change; other existing SEO tags are kept. [update_product_category]
helpNoReturn the action's full documentation and argument schema instead of running it
nameNoCategory name [create_product_category, update_product_category]
imageNoHosted image URL for the category card [create_product_category, update_product_category]
actionYesWhich operation to run
hiddenNoHide (true) or show (false) the category [update_product_category]
parent_idNoParent category id for a sub-category [create_product_category]
descriptionNoCategory description [create_product_category, update_product_category]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already flag this as mutating and destructive, and the description is consistent with that via delete_product_category. However it never says deletions are permanent, whether deleting a category orphans its products, or what permissions are required. The `help:true` discovery mechanism is a genuinely useful behavioral addition.

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?

Front-loaded with the dispatch instruction, then a tight bullet list, one line per action. The bullets partly restate the action names ('list_categories: List all product categories'), which is mild redundancy but aids scanning.

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?

With 10 parameters, a nested `seo` object, and no output schema, the agent still doesn't know what list_categories returns or how destructive deletes behave. The `help:true` mechanism partially compensates by promising full per-action documentation on demand.

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 every parameter already carries an action tag such as '[update_product_category]', so the schema does the heavy lifting. The description adds no format, default, or constraint details beyond restating the action list, which matches the baseline of 3.

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 this is a category-management dispatcher and enumerates all four operations with distinct verbs and resources (list, create, update, delete). Each action name maps directly to a clear outcome, so an agent can tell what the tool does 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?

It explicitly says to pick an operation via `action` and pass that action's arguments, and documents the `help:true` escape hatch for full per-action documentation. It even gives a reason for create ('so grid-category / a category page has something to show'). What is missing is any exclusion or routing guidance versus siblings like `product` or `collection`.

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