Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_section

Append a validated section to an existing page's source, preview changes with dry-run, or save while preventing ID collisions.

Instructions

Append a section to an EXISTING page's source. Reads the current source, appends your section, validates, and (when dry_run=false) saves. The section is re-id'd to avoid collisions. Pass a section built with new_section, OR template:{ category_id, id } to insert a library section (list_section_templates). Two-step safety: dry_run=true (default) previews; dry_run=false saves.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNoPreview only (true) or save (false)
page_idYesTarget page id
sectionNoA section node (from new_section) — object or JSON string
templateNoInsert a library section instead (ids from list_section_templates)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.34.1
    • addedInput schema / properties / template
      Added value: +{
+  "additionalProperties": false,
+  "description": "Insert a library section instead (ids from list_section_templates)",
+  "properties": {
+    "category_id": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}
  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 state readOnlyHint=false and destructiveHint=false; the description goes well beyond by disclosing the full read-append-validate-save pipeline, the re-id step to avoid collisions, and the dry_run default. This is the kind of operational detail an agent needs before committing a write.

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?

Three tight sentences, front-loaded with the verb+scope, then sourcing rules, then the safety workflow. No filler or restated name/title content.

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 nested-object mutation tool this is nearly complete: sourcing, re-id behavior, and the two-step save flow are all present. The only gap is that with no output schema, the description never indicates what is returned (e.g., validation results or the new section id).

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 description coverage is 100%, so baseline is 3, but the description adds genuine value by cross-referencing which sibling tools produce each input ('section built with new_section', 'template ... from list_section_templates') and reaffirming dry_run's default-true preview semantics.

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 ('Append a section to an EXISTING page's source') with explicit scope. The capitalized 'EXISTING' and the note that the id is re-generated distinguish it from new_section (which builds a section) without needing the schema.

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?

Clearly routes the agent: build a section with new_section, or supply template:{category_id,id} from list_section_templates, and explains the dry_run=true default preview workflow. It does not, however, contrast itself against similar mutators like add_draft_section or update_page_source, so the 'when-not' side is only partially covered.

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