Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

clone

Copy an existing web page into native sections, or extract its text and images as a blueprint to rebuild or migrate storefront content.

Instructions

Copy an existing web page as native sections (clone_page), or read a page's text/images as a blueprint (ingest_*). Pick the operation with action and pass that action's arguments (help:true returns its full documentation and schema).

  • clone_page: Clone a web page into NATIVE sections (text/image/button/form/video/container rows — no embed, no custom code).

  • get_clone_script: Get the capture script for clone_page: run it inside the source page with YOUR browser tool when clone_page can't open the page itself (remote server, no local Chrome, a page be…

  • ingest_url: Fetch a public URL and parse it into a structural blueprint (see ingest_html).

  • ingest_html: For a faithful copy of a live page use clone_page (native sections from the rendered layout).

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to clone (public URL) [clone_page, ingest_url]
helpNoReturn the action's full documentation and argument schema instead of running it
htmlNoRaw HTML to analyse [ingest_html]
widthNoCapture width in px (default 1440) [clone_page]
actionYesWhich operation to run
snapshotNoResult of the get_clone_script script (object or JSON string), instead of url [clone_page]
skip_chromeNoLeave out the source's header/footer/nav (use the site's global ones). [clone_page]
rehost_imagesNoUpload images (and svg icons as PNG) to the WebCake CDN (default false) [clone_page]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint=false annotation already signals that this is not a pure read tool, and the description adds some useful context: clone_page produces native sections rather than embeds/custom code, and rehost_images uploads assets to a CDN. However, it does not clarify whether clone_page creates or modifies a page, what permissions are required, or what the high-level side effects are.

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 definition is front-loaded with a useful summary and then uses bullets to organize the four actions, which suits a dispatcher-style tool. There are some malformed or truncated portions, and the final bullet is confusing because it is labeled ingest_html but primarily redirects to clone_page.

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?

Given four actions and eight parameters, the description covers most selection and invocation needs, and the input schema is richly documented. It remains incomplete because ingest_html is not properly explained, the get_clone_script guidance is cut off, and the mutation behavior of clone_page is not fully described.

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 schema already documents all parameters. The description adds meaningful action-level semantics by grouping parameters under the operation they apply to and explaining the purpose of each action; it does not add much detail beyond the schema for individual parameters such as snapshot or width.

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?

The opening line clearly states the two core modes: copying a page into native sections (clone_page) and reading a page as a blueprint (ingest_*). It distinguishes the main operations, but the ingest_html bullet does not actually describe that action's purpose and instead redirects to clone_page.

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

Usage Guidelines4/5

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

The description gives explicit routing guidance for several actions, including when to use get_clone_script instead of clone_page and when to prefer clone_page over ingest_html for a faithful live copy. It is not fully complete because it never states when ingest_html should be used, and the get_clone_script condition is truncated.

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