Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_my_sites

Read-only

Lists the current account's personal sites so you can find a site_id before switching; use filter all for active sites or removed for trash.

Instructions

List the current account's PERSONAL sites (team sites are not included). Use this to find a site_id before switching. filter: "all" = active sites (default), "removed" = sites in trash. Each site has status, published_at (set at creation — not proof of publishing), slug, primary domain and has_custom_domain (verified, live, non-default domain). For plans use get_site_subscription / count_my_sites.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
termNoSearch by site name, site id or domain
limitNoItems per page
filterNo"all" (active, default) or "removed" (trash)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.36.1
    • addedInput schema / properties / filter
      Added value: +{
+  "description": "\"all\" (active, default) or \"removed\" (trash)",
+  "enum": [
+    "all",
+    "removed"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / term / description
      Previous value: -"Search by site name"New value: +"Search by site name, site id or domain"
  2. First observedv1.31.8

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does so well: it discloses the personal-vs-team scope boundary, the trash vs active filter semantics, and per-field meanings including the important caveat that published_at is set at creation and is NOT proof of publishing. That caveat is exactly the kind of trap an agent would otherwise fall into.

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?

Front-loads the scope and use case, then the filter, then the return fields, then the sibling routing. It is dense and slightly run-on (the field list is packed with parenthetical caveats), but every clause carries information an agent needs.

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?

With no output schema, the description takes on return-value documentation itself and does it — status, published_at, slug, primary domain, has_custom_domain. Combined with the filter semantics and the sibling routing, an agent has everything needed to call this correctly.

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 coverage is 100%, so page, limit, term and filter are already documented in the schema. The description restates the filter enum meanings but adds nothing about term matching behavior or pagination interpretation, so it does not exceed the baseline.

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 and resource (list sites) and immediately narrows scope: PERSONAL sites only, team sites excluded. The 'find a site_id before switching' clause ties it to a concrete job, and naming get_site_subscription / count_my_sites separates it from the other site-listing/site-info siblings.

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 an explicit use case (locate site_id, then switch_site) and routes plan-related questions to get_site_subscription / count_my_sites, plus an implicit exclusion for team sites. An agent can pick this tool over its siblings without opening any schema.

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