Skip to main content
Glama
vuluu2k

WebCake Landing MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_section

Appends one or more section nodes to the end of an existing page's page array, server-side: only the new sections are sent, and the backend rejects element ids that already exist on the page. The sections are validated first.

Instructions

Appends one or more section nodes to the end of an existing page's page array, server-side: only the new sections are sent, and the backend rejects element ids that already exist on the page. The sections are validated first. dry_run defaults to true: it validates, caches the payload under a draft_id and previews the request; dry_run:false appends. A validation failure also returns a draft_id, which patch_page accepts for element-level fixes. Section-level saves cannot change page settings, so font weights that need new font links are reported in font_weights_notice. Requires Webcake credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoDefault TRUE — validate the section(s) and preview the request without writing. Set false to actually append.
page_idYesThe page id to append to (from create_page or list_pages; must be owned by the account).
draft_idNoA draft id returned by a previous add_section call (dry_run=true or validation failure). Loads the cached section payload, so the sections are not re-sent.
sectionsNoOne section node, or an array of section nodes, appended to the end of `page` (object/array or JSON string). Each is a normal section element { id, type:'section', responsive, children, … } with a unique id; sections stack vertically after the existing ones. Nodes may be sparse — omitted properties/runtime/empty events and children/per-breakpoint config are filled from factory defaults. Required unless draft_id is supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.11
    • changedInput schema / properties / draft_id / description
      Previous value: -"A draft id returned by a previous add_section call (dry_run=true or validation failure). Loads the cached section payload — no need to re-send the sections JSON. Use for dry-run → real call transitions and fix-after-error rounds."New value: +"A draft id returned by a previous add_section call (dry_run=true or validation failure). Loads the cached section payload, so the sections are not re-sent."
    • addedInput schema / properties / sections / anyOf
      Added value: +[
+  {
+    "additionalProperties": {},
+    "type": "object"
+  },
+  {
+    "items": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / sections / description
      Previous value: -"One section node, or an array of section nodes, to append to the END of `page` (object/array or JSON string). Each is a normal section element { id, type:'section', responsive, children, … } with a UNIQUE id; they stack vertically after the existing sections. Author SPARSE nodes — omit properties/runtime/empty events+children/per-breakpoint config; the server hydrates them from factory defaults. Required unless draft_id is supplied."New value: +"One section node, or an array of section nodes, appended to the end of `page` (object/array or JSON string). Each is a normal section element { id, type:'section', responsive, children, … } with a unique id; sections stack vertically after the existing ones. Nodes may be sparse — omitted properties/runtime/empty events and children/per-breakpoint config are filled from factory defaults. Required unless draft_id is supplied."
  2. First observedv1.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: the backend rejects duplicate element ids, sections are validated first, dry_run defaults to true and caches under a draft_id, validation failures still return a draft_id, font weights needing new links surface in font_weights_notice, and Webcake credentials are required. This is exactly the operational context an agent needs for a mutating tool.

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 append operation and the dry_run default before secondary details, and every sentence carries information. It is dense and slightly long, but no sentence is wasted.

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?

No output schema exists, and the description covers the key return signals (draft_id on validation failure, font_weights_notice) plus credential requirements. It does not fully describe the shape of the dry_run preview response, a minor gap for a server-side mutation.

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 baseline is 3, but the description adds cross-cutting meaning: dry_run's default and dual behavior, draft_id's cache-loading purpose, its acceptance by patch_page, and the sparse-node filling from factory defaults. It largely echoes the schema for the core fields, keeping it out of the top band.

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 — appending section nodes to an existing page's `page` array — and clarifies it is server-side with only new sections sent. It also names patch_page as the sibling for element-level fixes, so an agent can distinguish it from other write tools without opening a 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?

Explains when the tool applies (appending to an existing page) and routes element-level fixes to patch_page, plus documents the dry_run-first workflow. It stops short of an explicit when-not-to-use statement versus siblings like create_page or update_page.

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