Skip to main content
Glama

sb_page_create

Creates a Store Builder page with a chosen type, slug, locale, and optional seed content, enabling routes like /checkout or /products/{slug} to resolve.

Instructions

A store type (product, category, search, blog, post, complete, account) 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.

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": {
      "name": "<name>"
    },
    "name": "sb_page_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
seedNoDefault true; false creates a blank page.
slugNo
typeNoomit: inferred from the name (about/contact/policy/faq), else page; sb_page_list lists every type
chromeNoCarry the site's header and footer, default true
localeNovi or en — a store seed's wording; defaults to the site's language, else vi.
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.89.0
    • changedInput schema / properties / locale / description
      Previous value: -"vi (default) or en — the complete page's wording."New value: +"vi or en — a store seed's wording; defaults to the site's language, else vi."
  2. Changed1 schema field changedv0.69.0
    • changedInput schema / properties / type / description
      Previous value: -"page (default); sb_page_list lists every type and where each is served"New value: +"omit: inferred from the name (about/contact/policy/faq), else page; sb_page_list lists every type"
  3. Changed1 schema field changedv0.60.1
    • changedInput schema / properties / type / description
      Previous value: -"page (default), checkout, product, category, post, course"New value: +"page (default); sb_page_list lists every type and where each is served"
  4. Changed1 schema field changedv0.25.0
    • addedInput schema / properties / chrome
      Added value: +{
      +  "description": "Carry the site's header and footer, default true",
      +  "type": "boolean"
      +}
  5. 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"
      +}
  6. 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"
      +]
  7. First observedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful behavior — that store types carry bound content like the buy box and that missing published pages cause 404s — but it does not describe persistence, idempotency, or what the created page/response contains.

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

Conciseness3/5

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

It is short and front-loads type information, but the syntax is dense and jargon-heavy ('arrives with the document the editor gives a merchant', 'bound buy box'), which costs comprehension. Most sentences carry information, but the phrasing obscures rather than streamlines.

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

Completeness2/5

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

For an 11-parameter creation tool with a nested settings object, no output schema, and only 45% schema coverage, the description leaves too much undocumented. Key creation options and the return behavior are unexplained, making it inadequate given the tool's complexity.

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 only 45% across 11 parameters, so the description must compensate. It usefully enumerates the type values (product, category, search, blog, post, complete, account) despite zero schema enums and clarifies slug/type routing, but chrome, locale, headline, settings, site_id, is_homepage, dry_run, and name receive no additional meaning.

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

Purpose3/5

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

The name and route references imply page creation, but the description never states the core verb+resource plainly — it opens with 'A store type ... arrives with the document', which is hard to parse. It does specify available types and their distinct behavior, distinguishing it from siblings like sb_page_open and sb_page_list, but an agent must infer that this tool creates a page.

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?

It gives a conditional ('seed:false for blank') and points to sb_page_open for seeding ROOT, which is genuine when-to-use routing. However, it never explains when to choose create versus sb_page_update or sb_duplicate, and prerequisites (auth, site context) are only implied.

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