Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_app_review

Update a product-review app's settings by passing its subscription ID and full settings object to change shop info, auto-approve, or display options.

Instructions

Update the product-review app's settings (e.g. shop_info, auto-approve, display options). Pass the review app's subscription id (get_app with type "product_review") and the full settings object.

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": {
      "id": "<id>",
      "settings": "<settings>"
    },
    "name": "update_app_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReview app subscription id (get_app type=product_review)
settingsYesReview app settings object, e.g. { "shop_info": { ... }, "auto_approve": true }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint=false annotation already flags this as a mutation, so the bar is lower. The description earns credit for "Pass ... the full `settings` object," which hints at replacement semantics rather than a merge, but it does not spell out whether omitted keys are cleared, whether changes are reversible, or what permissions are needed.

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?

Two sentences with no filler; the purpose is front-loaded and the id-lookup instruction follows immediately. Every sentence carries weight, though the parenthetical field list is somewhat loose.

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 2-parameter mutation tool with full schema coverage, an annotation flagging intent, and no output schema, the description covers purpose, how to obtain the id, and the expected settings payload. Only the write semantics (replace vs. merge, what gets destroyed) remain thin.

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%, so both parameters are already documented in the schema and the description largely restates the id guidance. The "full settings object" phrasing adds a mild semantic nuance (whole-object replacement) but no field-level detail beyond the schema example.

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 and resource ("Update the product-review app's settings") and names the kinds of fields affected (shop_info, auto-approve, display options). It is distinguishable from the generic update_app sibling by the product-review scope, though it never explicitly says how it differs from update_app.

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?

Adds a useful retrieval hint for the id (get_app with type "product_review"), which is contextual guidance rather than pure when-to-use. It never states when to prefer this over update_app or what preconditions must hold for the review app to accept settings.

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