Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_promotions

Read-only

Find and filter storefront promotions by keyword, type, time status, or activation state across all pages. Use it to locate specific campaigns and check whether each is synced with the POS system.

Instructions

Search/filter ALL promotions (every page): by keyword, type, time status (coming_soon/in_progress/finished), active flag. Rows carry pos_id (non-null = synced with POS)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_promotions"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoSearch by promotion name
typeNoFilter by type: normal, same_price, coupon, coupon_id_multiple_times, discount_by_coupon_id, promotion_order, promotion_category, x_get_y_prod, x_get_y_category
statusNoFilter by time status: 1=coming_soon, 2=in_progress, 3=finished
is_activatedNoFilter by active status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.36.1
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Items per page",
-  "type": "number"
-}
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number",
-  "type": "number"
-}
  2. First observedv1.31.8

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the result set spans all pages rather than a single page, and each row carries pos_id whose non-null value signals POS sync — context an agent could not get from structured fields.

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?

Two short sentences, zero filler, with the scope constraint ('ALL ... every page') front-loaded before the filter list. The parenthetical gloss on pos_id is compact and high-value.

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?

With no output schema, the description correctly spends words on the notable return field (pos_id semantics). Scope and filters are fully covered; only minor gaps remain, such as result ordering and whether results are capped despite the 'every page' claim.

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 coverage is 100%, so all four parameters are already documented, including the full type enumeration and the 1/2/3 status mapping. The description only restates the four filter dimensions in prose without adding syntax, defaults, combination behavior, or match semantics, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Search/filter ALL promotions') and scopes it explicitly with '(every page)', which is the key differentiator from siblings like list_promotions or get_active_promotions. It never names those siblings directly, so the differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The '(every page)' phrasing implies 'use this when you need the complete set,' and the enumerated filter dimensions hint at narrowing use cases. However, no alternative tool is named and there are no explicit when-not conditions, so the agent must infer that get_promotion is for single-record lookup and list_promotions for paged retrieval.

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

Deploy Server

Other Tools