Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k

create_product

Add a product to your storefront with name, price, and images. For multi-SKU items, define attributes and variations. The backend generates the slug and publishes it automatically.

Instructions

Create a product so the storefront has real merchandise (grid-product / slider-product bindings need this). Simple use: pass name + price (+ images, category_ids). One default variation with the price/stock is created for you. Advanced use: pass attributes (e.g. Color/Size) + variations for a multi-SKU product. Images must be HOSTED URLs — get them from search_images or upload_images first. The backend generates id, slug and publishes the product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuNoSKU / custom_id for the simple case (auto-generated if omitted)
nameYesProduct name
priceNoSelling price (used when you don't pass variations). Required unless variations are given.
stockNoStock quantity for the simple single-variation case
imagesNoHosted image URLs (search_images/upload_images). First image becomes the product thumbnail.
attributesNoVariant axes, e.g. [{name:'Color',values:['Đen','Trắng']},{name:'Size',values:['S','M','L']}]
variationsNoExplicit per-SKU variations. Omit to auto-build one from price/stock/sku.
descriptionNoFull product description (HTML allowed) — binds to product::description on the detail page.
category_idsNoProduct category IDs to file the product under (from create_product_category / list_categories)
original_priceNoList/compare-at price for the simple single-variation case
short_descriptionNoShort description / tagline (HTML allowed) — binds to product::short_description on cards + the detail page. Set this so cards aren't blank.
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses key behaviors: backend generates id/slug, publishes the product, auto-creates a default variation, and requires hosted URLs. It does not cover auth/error cases but sufficiently reveals side effects.

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, with three sentences covering purpose, usage modes, and key constraints. Every sentence adds value, and the line breaks for simple/advanced usage improve readability.

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?

For a tool with 11 parameters and no output schema, the description provides high-level workflow context and prerequisites (hosted images, category IDs). It does not detail return values, but the schema already covers parameter specifics, making this adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions, so baseline is 3. The description adds conceptual meaning by grouping parameters into simple vs. advanced usage and explaining relationships (e.g., name+price for simple, attributes+variations for multi-SKU), which goes 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 clearly states the tool creates a product for storefront merchandise, with a specific verb and resource. It distinguishes from siblings like update_product/delete_product by emphasizing creation and the resulting published product.

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?

Provides explicit usage guidance: 'Simple use' and 'Advanced use' with parameter combinations, and instructs to obtain hosted URLs from search_images/upload_images. It implies but does not explicitly name alternatives like update_product for modifications, so a 4 is appropriate.

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