Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

promotion

Read-only

Manage and inspect store discounts, coupons, active offers, and combo bundles by listing, searching, or retrieving full details and attached products.

Instructions

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

  • list_promotions: List ALL promotions/discounts of the site (every page is fetched for you).

  • search_promotions: Search/filter ALL promotions (every page): by keyword, type, time status (coming_soon/in_progress/finished), active flag.

  • get_promotion: Get full promotion details by ID: name, type, schedule, discount rules, coupon settings, items, bonus products, etc.

  • get_promotion_items: Get products/variations/categories attached to a promotion.

  • get_active_promotions: Get all currently active promotions (is_activated=true and within start_time/end_time range)

  • list_combos: List all combo/bundle products of the site.

  • get_combo_items: Get items (products/variations) and bonus products that compose a combo.

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": "promotion"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPromotion ID [get_promotion, get_promotion_items]
helpNoReturn the action's full documentation and argument schema instead of running it
pageNoPage number [get_promotion_items, list_combos]
termNoSearch by promotion name [search_promotions, list_combos]
typeNoFilter by type: normal, same_price, coupon, coupon_id_multiple_times, discount_by_coupon_id, prom… [search_promotions]
limitNoItems per page [get_promotion_items, list_combos]
actionYesWhich operation to run
statusNoFilter by time status: 1=coming_soon, 2=in_progress, 3=finished [search_promotions]
is_activatedNoFilter by active status [search_promotions]
include_guideNoInclude promotion type reference guide [list_promotions, list_combos]
combo_product_idNoCombo product ID [get_combo_items]
is_variation_bonusNoWhether bonus items are variation-based [get_combo_items]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and nothing in the description contradicts that; the tool is purely read-only. The description adds genuinely useful behavior notes ('every page is fetched for you' for list/search, and help:true returning the action's documentation and schema), but says nothing about permissions, rate limits, or response shape for most actions.

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 framing sentence sets the action-dispatch pattern, followed by a tight one-line-per-action bullet list with zero redundant prose. The opening line is slightly colloquial ('pass that action's arguments') but nothing is wasted.

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?

Covers every action in a 7-way discriminator over 12 parameters, which is the main risk of miscalling. Since there is no output schema, describing return content matters, and it does this well for get_promotion and get_combo_items but only generically for the list/search actions.

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% and each property already tags which action consumes it, so the schema carries the parameter burden. The description still adds value by mapping actions to their argument intents (status = coming_soon/in_progress/finished, is_activated, term for name search), though it does not explain the enum expansion of type or the pagination defaults.

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?

States a specific verb+resource (promotions and combos) and then enumerates all seven operations with concrete objects: list all promotions, search by filters, fetch by ID, fetch attached items, fetch active-only promotions, list combos, fetch combo items. An agent can distinguish each sub-operation from the others without opening the schema, and the domain is clearly distinct from sibling tools like product or order.

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 action list effectively routes usage: list_promotions for everything, search_promotions when keyword/type/status/is_activated filters are needed, get_active_promotions for the currently running subset, get_promotion by ID. That is clear dispatch guidance, but there is no explicit exclusion or 'prefer X over Y' statement, and the boundary between list_promotions and search_promotions with no filters is left implicit.

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