set_landing_page_section
Set a field within a landing page section using dot-path notation, or replace the entire section with new content. Each call creates a new draft version for the page.
Instructions
Set one field on a landing page section (dot-paths in field supported, e.g. 'plans.0.ctaUrl'), or replace a whole section with replaceSection=true. Pass the bare content-section key (e.g. 'hero', 'features', 'pricing') — the server maps it into the page's content tree. Top-level roots like slotMap, config, navigation, siteMetadata are also accepted as-is. Each call creates a new draft version — for many related changes across a page, prefer vibe_edit_landing_page instead. Example: section='hero', field='title', value='New headline'.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Name for the new version | |
| slug | Yes | Landing page slug | |
| field | No | Dot-path field within the section to set, e.g. 'title' or 'plans.0.ctaUrl'. Required unless replaceSection=true. | |
| value | Yes | New value for the field (or the whole section when replaceSection=true). May be any JSON type — string, number, boolean, null, array, or object — sent verbatim, not stringified. | |
| section | Yes | Bare section key. For content sections use e.g. hero, features, pricing, cta, faq — the server maps these into the page's content tree. Top-level roots like slotMap, config, navigation, siteMetadata are also accepted. | |
| description | No | Description for the new version | |
| replaceSection | No | Replace the entire section with `value` instead of setting one field |