Skip to main content
Glama
vuluu2k

sbuilder-mcp

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sb_page_create

Create storefront pages for product, category, checkout, blog, post, or course types with default or blank content, locale, slug, and homepage settings for publishing.

Instructions

A store type (product, category, search, blog, post, complete) arrives with the document the editor gives a merchant — product carries the whole bound buy box; seed:false for blank. Any other type is empty and sb_page_open seeds its ROOT. TYPE is the route: /checkout and /products/{slug} need a PUBLISHED page of that type or they 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
seedNoDefault true; false creates a blank page.
slugNo
typeNopage (default), checkout, product, category, post, course
chromeNoCarry the site's header and footer, default true
localeNovi (default) or en — the complete page's wording.
dry_runNo
site_idNo
headlineNoThe complete page's thank-you line.
settingsNo
is_homepageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.0
    • addedInput schema / properties / chrome
      Added value: +{
+  "description": "Carry the site's header and footer, default true",
+  "type": "boolean"
+}
  2. Changed3 schema fields changedv0.16.0
    • addedInput schema / properties / headline
      Added value: +{
+  "description": "The complete page's thank-you line.",
+  "type": "string"
+}
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "vi (default) or en — the complete page's wording.",
+  "type": "string"
+}
    • addedInput schema / properties / seed
      Added value: +{
+  "description": "Default true; false creates a blank page.",
+  "type": "boolean"
+}
  3. Changed4 schema fields changedv0.12.0
    • addedInput schema / properties / is_homepage
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / slug
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "page (default), checkout, product, category, post, course",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "site_id",
-  "name"
-]New value: +[
+  "name"
+]
  4. First observedv0.1.4

TDQS

D1.7/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds little beyond that. It mentions 'seed:false for blank' and 'Any other type is empty', but these are cryptic and do not clarify side effects, required permissions, or the nature of the write operation. No contradiction exists, but disclosure is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense, cryptic sentence that is hard to parse. It front-loads jargon ('store type', 'bound buy box', 'ROOT') without definitions. It is not concise in a helpful way; it sacrifices clarity for brevity.

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

Completeness1/5

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

With 11 parameters, a nested object, and no output schema, the description is severely inadequate. It does not explain the full creation flow, what happens to each page type, how routing works in practice, or any post-creation effects. An agent cannot reliably call this tool based on the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 45% (5 of 11 params have descriptions). The tool description adds some meaning for 'seed' (blank page) and 'type' (route mapping), but it does not compensate for the many undocumented parameters like 'slug', 'site_id', 'dry_run', or 'settings'. The added value is insufficient for the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never explicitly states that this tool creates a page. It discusses 'store type', documents, routing, and references to sb_page_open, but the primary action (creating a page) is only implied. The verb is absent, making the purpose vague and confusing.

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

Usage Guidelines1/5

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

There is no clear guidance on when to use sb_page_create versus alternatives. It mentions sb_page_open but only in the context of seeding roots, not as a decision point. No conditions or exclusions are provided, leaving the agent to guess.

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