LandingRabbit

Take the snapshotId of a previewed proposal and save it. It saves the proposal after the user approves the preview. brandId comes from list_brands. This tool refuses a proposal that has not been previewed. It overwrites the saved brand design and the affected Styles with the proposal. Send a new UUID as requestId for each new request. If you retry that request, reuse its requestId. A new request needs a new UUID even when the instruction is identical. It runs in the background and returns a jobId. Read the result with get_brand_design_result and never send the same request again while it runs.

approve_brand_design

Open the LandingRabbit web app (app.landingrabbit.com) in an embedded frame and sign the user in to it beside this conversation, on the brands list. Each call creates a new one-time sign-in link and a new app session. It needs a signed-in connection that allows editing.

open_landingrabbit_panel

Edit the full brand design: colours, fonts, buttons, spacing and layouts across sections and saved Styles. brandId comes from list_brands. A brand-wide change shows first as a preview on the brand page and is approved after the user reviews it. Call get_brand_design first to get the sectionIds. This tool takes one short instruction: whether the change covers all sections and Styles, one section and its Styles, or one or a few Styles, then what changes, as properties and values, for example colours, font sizes, spacing. Keep every choice the user made, including anything they singled out or ruled out. Drop the rest of their wording and add nothing of your own, because everything in the instruction is read as part of the change. Write it as short and specific as "hero title text size 3rem, dark green". Pass targetSectionIds to change specific sections or Styles, or leave them out to change the whole brand. Send a new UUID as requestId for each new request. If you retry that request, reuse its requestId. A new request needs a new UUID even when the instruction is identical. It runs in the background and returns a jobId. Read the result with get_brand_design_result and never send the same request again while it runs. A brand-wide edit returns a proposal. Show it with preview_brand_design, then save it with approve_brand_design after the user approves the preview. To revise the proposal, call this tool again without targetSectionIds. A targeted edit is refused while a proposal is pending. A targeted edit saves right away and overwrites the current values of the sections and Styles it names. A brand-wide edit saves nothing until it is approved. A Style with bespoke HTML keeps its look through brand-wide styling changes because its HTML sets it, and the result names every such Style it reached.

change_brand_design

Drop the pending proposal of the brand. brandId comes from list_brands. A brand-wide change shows first as a preview on the brand page and is approved after the user reviews it. This tool removes the pending proposal and its pending preview from the brand page. The proposal cannot be approved after that. Make a new change with change_brand_design to start again.

discard_brand_design

This tool reads a section's structure and current design. brandId comes from list_brands. Call get_brand_design first to get the sectionIds and to see which sections already have a custom design. Pass templateId to read a specific custom Style. Without it, the tool reads the Style that the section shows. Call it before you save or update custom HTML. It changes nothing.

get_brand_custom_design

This tool returns the authoring guide (data.customDesignGuide) for custom HTML designs. brandId comes from list_brands. It needs no section. Call it before you write custom HTML. It changes nothing.

get_brand_custom_design_guide

Read the brand design. brandId comes from list_brands. Call it first: it lists every section with its sectionId, the Style it uses, whether that Style has bespoke HTML, any pending proposal and any edit still running. It changes nothing.

get_brand_design

Read the progress or the result of a change_brand_design or approve_brand_design job. brandId comes from list_brands. This tool takes the jobId that the job returned. It reads progress or the finished result, and it changes no saved design. Call it about every 15 seconds while the job is queued or running, and read the result or error when it finishes. A paused job kept everything it finished and says why it stopped: relay that, and call resume_brand_design with its jobId when the user wants it to continue. An unknown jobId returns whatever is running now and any pending proposal, which is context for finding the request, not proof the job finished.

get_brand_design_result

Open the LandingRabbit web app (app.landingrabbit.com) in an embedded frame and sign the user in to it: the brands list or one brand's design page. Each call creates a new one-time sign-in link and a new app session, so open the app only when it is not open. When it is open, use app_navigate instead. This tool changes no brand, but the user can edit brands in the opened app. It needs a signed-in connection that allows editing. A connection with an API key gets an error.

open_landingrabbit

Lists the brands this account owns, with brandId, name and status. Call it before edit_brand_design, which needs a brandId.

list_brands