Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k

delete_product_category

Delete one or more product categories from a WebCake storefront by specifying their IDs. Removes categories and their associations to keep the catalog up to date.

Instructions

Delete one or more product categories by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesCategory ids to delete
Behavior2/5

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

With no annotations provided, the description needs to disclose behavioral traits such as whether deletion is permanent, whether it cascades to related products or subcategories, or any required permissions. The description only states the core action without any such context.

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 a single, focused sentence that conveys the action immediately, with no unnecessary words.

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

Completeness2/5

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

Although the tool is simple, it is destructive and no annotations or output schema exist. The description lacks any mention of irreversibility, side effects, or what happens to associated products, leaving the agent with insufficient context for safe 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?

The input schema already documents the 'ids' parameter with its type and description, covering 100% of parameters. The description adds only a slight clarification that deletion is 'by id' and supports 'one or more', which is already implied by the array type, so it adds marginal value.

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 clearly states that the tool deletes one or more product categories identified by id, using the specific verb 'Delete' and the resource 'product categories'. This distinguishes it from sibling tools like delete_product, delete_page, or update_product_category.

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 provides no guidance on when to choose this tool over alternatives, such as when it is appropriate to delete a category versus archival, or any prerequisites. There are no exclusions or alternative recommendations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vuluu2k/webcake-storefront-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server