Skip to main content
Glama

Sitelas

by com.sitelas
OverviewDiscussionsAdmin

Add a section

add_section

Add a complete, hand-fixture-quality section to a page from a FLAT description — no node-tree authoring. Pick a kind, pass page_slug + the copy fields (eyebrow, heading, body, CTAs) and, for list-based kinds, an items[] array of flat cards/rows. The tool builds a correct section > container > stack > [...] subtree (theme tokens, Lucide icons, responsive grids, real spacing, every text/CTA independently editable) and splices it into the page, saved as one draft. Kinds & use-when: hero (page-opening headline+CTAs); features (icon/title/body card grid); content (long-form block); cta (centered band CTA); gallery (image grid); testimonials (quote cards); stats (count-up numbers); pricing (tier cards, highlight one); faq (Q&A list); logo-strip ('trusted by' logos); pull-quote (centered editorial quote); team-grid (people cards); split-image-text (image + copy split); process-steps (numbered steps); feature-split (copy + bullet list + image); newsletter (inline email signup band); comparison (with-us vs without); metrics-band (stats on accent band); banner-cta (full-width accent CTA); contact-form (copy + name/email/message form). Use this — not patch_fixture — to populate a page or add a section in-editor. For surgical edits to existing nodes use patch_nodes; for bespoke structure use insert_nodes (claude.ai only).

Input Schema

NameRequiredDescriptionDefault
bodyNoSupporting paragraph (hero subtitle / content body / cta body).
kindYesSection archetype. Use when: • hero — page-opening eyebrow + big headline + CTAs; `layout` makes it split (photo beside) or full-bleed (photo behind). • features — heading + icon/title/body card grid (items[]: icon,title,body). • content — heading + long-form body (single column). • cta — centered heading + body + buttons on a muted band. • gallery — heading + image grid (items[]: image_url, title=alt). • testimonials — quote cards (items[]: body=quote, title=name, meta=role, image_url=avatar). • stats — row of big count-up numbers (items[]: value, label). • pricing — 2-3 tier cards (items[]: title, price, period, body, cta_label, cta_href, featured). • faq — two-column Q&A (items[]: title=question, body=answer). • logo-strip — quiet 'trusted by' row of logos (items[]: image_url). • pull-quote — centered editorial quote (body=quote, eyebrow=attribution). • team-grid — people cards (items[]: image_url, title=name, meta=role, body=bio). • split-image-text — image one side, copy + CTAs the other (image_url or items[0].image_url). • process-steps — numbered steps (items[]: title, body, icon). • feature-split — copy + icon-bullet list one side, image the other (items[]: icon,title,body). • newsletter — heading + pitch + inline email signup form on a band. • comparison — two columns, 'with us' (items[]: body/title) vs 'without' (items[]: meta). • metrics-band — stats on a full-width accent band (items[]: value, label). • banner-cta — full-width accent band, centered heading + inverted CTAs. • contact-form — copy one side, stacked name/email/message form the other.
nameNoWhat the section is, in the owner's words ('About us', 'Why choose us', 'Reviews'). Shown as the section's name in the editor, and how later tools recognise it. Defaults to the kind ('Split', 'Features').
itemsNoRepeated flat cards/rows — meaning depends on `kind` (feature cards, gallery images, testimonials, stats, pricing tiers, FAQ pairs, logos, team members, process steps, comparison rows, metrics). Up to 12.
layoutNokind=hero only — how the hero is arranged. 'centered' (default): text-only, centered. 'split': headline + buttons one side, image_url photo the other. 'full-bleed': image_url photo fills the section under a dark scrim with white text. 'split' and 'full-bleed' need image_url; without one the hero is centered.
eyebrowNoSmall label above the heading (hero/features).
headingNoSection heading / hero headline.
site_idYes
positionNoWhere on the page to add it. Default 'end'.
image_urlNoSingle image URL — the photo for a split / full-bleed hero, or for image-led kinds.
page_slugYesSlug of the page to add the section to, e.g. '/' or '/about'. Must be an existing page.
primary_cta_hrefNoPrimary button href (defaults to '#').
primary_cta_labelNoPrimary button label (hero/cta).
secondary_cta_hrefNoSecondary button href.
secondary_cta_labelNoSecondary button label (hero/cta).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare non-read-only, non-destructive, non-idempotent, closed-world behavior. The description adds the key state effect — it builds a subtree and 'splices it into the page, saved as one draft' — plus internal composition details (theme tokens, independently editable text/CTAs). It does not mention permission requirements or failure modes, so it falls short of a 5.

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-loaded: what the tool does and its key differentiator come first, followed by usage and routing. The 20-kind list duplicates the schema's kind enum description and adds length, but the overall structure is efficient for a 15-parameter tool.

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 complex write tool with 20 kinds and no output schema, the description covers selection, routing, and input shape well. Minor gaps remain around required site/page state and return behavior, though the schema and annotations cover most of that territory.

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 93%, so per-parameter meanings are already documented and the baseline is 3. The description adds only a high-level grouping ('copy fields', 'items[] array for list-based kinds') that largely restates what the schema already says.

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 ('add') and resource ('section') to a page, and immediately distinguishes itself from node-tree authoring. It also names the sibling tools it replaces for other tasks (patch_fixture, patch_nodes, insert_nodes), so an agent can select it without opening other schemas.

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?

Explicitly routes usage: 'Use this — not patch_fixture — to populate a page or add a section in-editor,' then names patch_nodes for surgical edits and insert_nodes for bespoke structure. It also maps all 20 kinds to concrete use-when conditions.

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

All Sitelas toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources