Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

collection

Destructive

Manage CMS custom data tables and their records: list, inspect, create, update columns, delete, and query by table name with filters, sorting, and pagination.

Instructions

CMS collections (custom data tables) and their records. Pick the operation with action and pass that action's arguments (help:true returns its full documentation and schema).

  • list_collections: List all database collections (tables) for the site.

  • get_collection: Get a specific collection's details including full schema (field names, types, constraints, references) and records

  • create_collection: Create a new collection (custom data TABLE).

  • update_collection_columns: Add or change a collection's custom columns.

  • delete_collection: Delete a collection (table) and all its records by id.

  • query_collection_records: Query records from a collection (custom data table) by table name.

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

Input Schema

NameRequiredDescriptionDefault
idNoCollection ID [get_collection]
helpNoReturn the action's full documentation and argument schema instead of running it
nameNoDisplay name. [create_collection]
pageNoPage number [list_collections, query_collection_records]
termNoSearch by collection name [list_collections]
limitNoItems per page [list_collections, query_collection_records]
whereNoFilter object, e.g. [query_collection_records]
actionYesWhich operation to run
columnsNoCustom columns to add, e.g. [create_collection, update_collection_columns]
order_byNoField to sort by (e.g. [query_collection_records]
table_nameNoTable name (snake_case, unique). [create_collection, query_collection_records]
collection_idNoCollection id (from list_collections / get_collection). [update_collection_columns, delete_collection]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare `destructiveHint: true` and `readOnlyHint: false`, so the baseline safety profile is provided. The description adds useful operation-level behavior, especially that `delete_collection` deletes a table and all its records and that create/update operations mutate tables and columns. It still omits permissions, confirmation requirements, and rate-limit behavior.

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?

The description is front-loaded and organized as a compact action list, which suits a polymorphic tool. It has minor repetition of phrases like "custom data table," but no significant wasted content.

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

Completeness3/5

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

For a complex 12-parameter, action-based tool with no output schema, the description names all available operations and the help mechanism. It does not describe return values, action-specific outcomes, or prerequisites, leaving those gaps to be covered by the schema and runtime docs.

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 the baseline is 3. The description adds the overall action-dispatch model and mentions `help:true`, but it does not add parameter-level meaning beyond the already complete 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 states the resource clearly: CMS collections (custom data tables) and their records. It then enumerates six concrete operations selected by `action`, so an agent can identify the tool's domain and capabilities without opening the schema.

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?

It explains the dispatch pattern: choose an operation with `action` and pass that action's arguments, with `help:true` returning full documentation and schema. However, it gives no guidance on when to use this tool versus related CMS/page/product tools, and it does not warn when destructive actions should be avoided.

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