Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_page_contents

Read-only

List multi-language translations for storefront pages and global sections. Filter by page ID and language code to read one page's translation content.

Instructions

List multi-language contents (translations) of the site's pages and global sections. Pass page_id + language_code to read one page's translation.

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_page_contents"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idNoPage ID — narrows the result to that page
language_codeNoWith page_id: return just that language's content map

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.34.1
    • addedInput schema / properties / language_code
      Added value: +{
+  "description": "With page_id: return just that language's content map",
+  "type": "string"
+}
    • changedInput schema / properties / page_id / description
      Previous value: -"Filter by Page ID"New value: +"Page ID — narrows the result to that page"
  2. First observedv1.31.8

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds that the tool spans both pages and global sections and returns content maps for translations, which is genuinely useful context. It still omits return shape, pagination, and ordering behavior, so it is adequate but not rich.

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 tight sentences with no filler: the primary enumeration is front-loaded and the narrowing instruction follows. Every sentence earns its place.

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 read-only listing tool with full schema coverage, no output schema, and two optional params, the description covers purpose, scope, and the key invocation pattern. It stops just short of explicitly routing the agent away from similar listing tools, which keeps it from a 5.

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 (including the combination semantics of page_id + language_code). The description restates that combination but adds no syntax, format, or default-value detail beyond it, so the baseline of 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?

Uses a specific verb ('List') and resource ('multi-language contents (translations) of the site's pages and global sections'), which is clearer than a bare 'contents' listing. It hints at the scope (pages + global sections) but does not name or differentiate from close siblings like list_pages or get_page_source, so the agent must infer the boundary.

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 second sentence gives a concrete invocation pattern ('Pass page_id + language_code to read one page's translation'), implying when to narrow the query. However there is no explicit when-to-use vs when-not, and no mention of alternatives such as list_pages for page metadata, so guidance is only implied.

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