Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_section_templates

Read-only

Browse designer-crafted section templates for storefront pages. Search or filter by category to find styled blocks, then insert and customize.

Instructions

Browse the designer-made section library (the editor's template picker): ready, styled blocks (hero, product showcase, testimonials, footer…) to start from instead of composing from scratch. No args → categories. With category_id and/or term → templates { id, name, thumbnail, kind }. Look at a thumbnail with invoke_tool('read_image', { url }), then insert a kind:"section" template with add_section({ page_id, template:{ category_id, id } }) and restyle it to the brand.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage (default 1)
termNoSearch template names
limitNoPer page (default 12)
category_idNoCategory id (from the no-arg call)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.34.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description's disclosure that the return shape varies by input (categories vs templates) and that templates carry { id, name, thumbnail, kind } adds real behavioral context beyond the safely-read signal. It could say more about scale/paging behavior, but is solid for a read-only browse tool.

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?

Three dense, front-loaded sentences: purpose first, then input-dependent behavior, then the end-to-end workflow. Every clause earns its place with no filler.

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

Completeness5/5

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

For a read-only, no-output-schema tool with full param coverage, this description is complete: it covers purpose, input branching, return fields, thumbnail inspection, and the downstream insertion/restyle path.

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%, so the baseline is 3, but the description goes beyond: it explains the no-arg default behavior and that category_id must come from the no-arg call, plus how category_id/term combine — context the schema's terse strings do not convey.

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 (Browse) and resource (designer-made section library / template picker) and enumerates concrete template kinds (hero, product showcase, testimonials, footer). It is clearly distinguishable from siblings like add_section (insertion) and list_elements without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit branch conditions: 'No args → categories' and 'With category_id and/or term → templates'. It also names the follow-on alternative workflow (read_image to preview, add_section to insert, then restyle), so an agent knows exactly when to use this versus the sibling tools.

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