Skip to main content
Glama
Sign In
swebsy-mcp

swebsy-mcp

Official
by swebsy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Replace page content

swebsy_replace_page_content
Destructive

Replaces every top-level section of the selected page with generated components to rebuild or redesign the entire page in one overwrite.

Instructions

Replace ALL top-level sections of the CURRENTLY SELECTED page with a generated list of components. This OVERWRITES the page — it does NOT create a new page (use create_page) and does NOT append a single section (use add_section). Use when the user asks to build/replace/redesign an entire page. Each top-level component should be wrapped in a container.

Input Schema

NameRequiredDescriptionDefault
planYesA 1-2 sentence summary of the sections you will create and why. This surfaces as an assistant message.
componentsYesTop-level page components (sections). Each should be wrapped in a container.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.14.1
    • changedInput schema / properties / components / items / properties / t / enum
      Previous value: -[
-  "container",
-  "layout-row",
-  "column",
-  "div",
-  "divider",
-  "heading",
-  "h1",
-  "h2",
-  "h3",
-  "h4",
-  "h5",
-  "h6",
-  "paragraph",
-  "link",
-  "link-block",
-  "badge",
-  "blockquote",
-  "list",
-  "ul",
-  "ol",
-  "li",
-  "list-item",
-  "span",
-  "text",
-  "textnode",
-  "image",
-  "video",
-  "iframe",
-  "audio",
-  "google-map",
-  "card",
-  "card-media",
-  "card-overlay",
-  "card-group",
-  "card-header",
-  "card-body",
-  "card-footer",
-  "swebsy-icon",
-  "gallery",
-  "lightbox",
-  "svg",
-  "svg-in",
-  "nav",
-  "navbar",
-  "navbar-brand",
-  "navbar-toggler",
-  "navbar-collapse",
-  "navbar-nav",
-  "nav-item",
-  "nav-link",
-  "breadcrumbs",
-  "btn",
-  "copy-button",
-  "dark-mode-switch",
-  "marquee",
-  "form",
-  "input",
-  "textarea",
-  "select",
-  "option",
-  "label",
-  "fieldset",
-  "legend",
-  "checkbox",
-  "radio",
-  "button"
-]New value: +[
+  "container",
+  "layout-row",
+  "column",
+  "div",
+  "divider",
+  "heading",
+  "h1",
+  "h2",
+  "h3",
+  "h4",
+  "h5",
+  "h6",
+  "paragraph",
+  "link",
+  "link-block",
+  "badge",
+  "blockquote",
+  "list",
+  "ul",
+  "ol",
+  "li",
+  "list-item",
+  "span",
+  "text",
+  "textnode",
+  "image",
+  "video",
+  "iframe",
+  "audio",
+  "google-map",
+  "image-compare",
+  "card",
+  "card-media",
+  "card-overlay",
+  "card-group",
+  "card-header",
+  "card-body",
+  "card-footer",
+  "swebsy-icon",
+  "gallery",
+  "lightbox",
+  "svg",
+  "svg-in",
+  "nav",
+  "navbar",
+  "navbar-brand",
+  "navbar-toggler",
+  "navbar-collapse",
+  "navbar-nav",
+  "nav-item",
+  "nav-link",
+  "breadcrumbs",
+  "btn",
+  "copy-button",
+  "dark-mode-switch",
+  "marquee",
+  "accordion",
+  "accordion-item",
+  "accordion-summary",
+  "form",
+  "input",
+  "textarea",
+  "select",
+  "option",
+  "label",
+  "fieldset",
+  "legend",
+  "checkbox",
+  "radio",
+  "button"
+]
    • changedInput schema / properties / components / items / properties / type / enum
      Previous value: -[
-  "container",
-  "layout-row",
-  "column",
-  "div",
-  "divider",
-  "heading",
-  "h1",
-  "h2",
-  "h3",
-  "h4",
-  "h5",
-  "h6",
-  "paragraph",
-  "link",
-  "link-block",
-  "badge",
-  "blockquote",
-  "list",
-  "ul",
-  "ol",
-  "li",
-  "list-item",
-  "span",
-  "text",
-  "textnode",
-  "image",
-  "video",
-  "iframe",
-  "audio",
-  "google-map",
-  "card",
-  "card-media",
-  "card-overlay",
-  "card-group",
-  "card-header",
-  "card-body",
-  "card-footer",
-  "swebsy-icon",
-  "gallery",
-  "lightbox",
-  "svg",
-  "svg-in",
-  "nav",
-  "navbar",
-  "navbar-brand",
-  "navbar-toggler",
-  "navbar-collapse",
-  "navbar-nav",
-  "nav-item",
-  "nav-link",
-  "breadcrumbs",
-  "btn",
-  "copy-button",
-  "dark-mode-switch",
-  "marquee",
-  "form",
-  "input",
-  "textarea",
-  "select",
-  "option",
-  "label",
-  "fieldset",
-  "legend",
-  "checkbox",
-  "radio",
-  "button"
-]New value: +[
+  "container",
+  "layout-row",
+  "column",
+  "div",
+  "divider",
+  "heading",
+  "h1",
+  "h2",
+  "h3",
+  "h4",
+  "h5",
+  "h6",
+  "paragraph",
+  "link",
+  "link-block",
+  "badge",
+  "blockquote",
+  "list",
+  "ul",
+  "ol",
+  "li",
+  "list-item",
+  "span",
+  "text",
+  "textnode",
+  "image",
+  "video",
+  "iframe",
+  "audio",
+  "google-map",
+  "image-compare",
+  "card",
+  "card-media",
+  "card-overlay",
+  "card-group",
+  "card-header",
+  "card-body",
+  "card-footer",
+  "swebsy-icon",
+  "gallery",
+  "lightbox",
+  "svg",
+  "svg-in",
+  "nav",
+  "navbar",
+  "navbar-brand",
+  "navbar-toggler",
+  "navbar-collapse",
+  "navbar-nav",
+  "nav-item",
+  "nav-link",
+  "breadcrumbs",
+  "btn",
+  "copy-button",
+  "dark-mode-switch",
+  "marquee",
+  "accordion",
+  "accordion-item",
+  "accordion-summary",
+  "form",
+  "input",
+  "textarea",
+  "select",
+  "option",
+  "label",
+  "fieldset",
+  "legend",
+  "checkbox",
+  "radio",
+  "button"
+]
  2. First observedv0.8.0

TDQS

A4.5/5.0
Behavior4/5

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

With destructiveHint already true, the description adds important scope: it overwrites ALL top-level sections of the currently selected page and warns that each component should be wrapped in a container. It stops short of discussing reversibility, undo, or permissions, but the destructive footprint is clearly disclosed.

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?

The description is compact and front-loaded with the destructive scope before alternatives and usage guidance. Every sentence carries selection or invocation value.

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?

For a two-parameter tool with rich schema coverage and destructive annotations, the description supplies the missing operational context: target page, replacement scope, forbidden alternative interpretations, and top-level wrapping. Nothing needed to choose or invoke the tool correctly is absent.

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 description coverage is 100%, so the schema already documents `plan` and the recursive component structure in detail. The description adds only the structural expectation that top-level components be wrapped in a container, which is useful but minimal, so baseline 3 is appropriate.

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?

The description states a specific verb and resource: replace ALL top-level sections of the CURRENTLY SELECTED page. It explicitly distinguishes this operation from creating a page and from appending a single section, naming the relevant alternatives.

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?

It gives clear when-to-use guidance: 'Use when the user asks to build/replace/redesign an entire page.' It also explicitly states when not to use it ('does NOT create a new page', 'does NOT append a single section') and routes to `create_page` and `add_section`.

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