weave-webmcp.vercel.app

weave_propose_changes

Propose several related edits as ONE reviewable change, instead of applying them one at a time. Use this for any request that touches more than one element — rewriting a hero, restructuring a page, adding and then populating a section. The proposal is shown to the human, who can edit individual values, skip parts of it, apply it or reject it; accepted operations then commit together as one undoable revision. Nothing changes on the page until the human applies it. The proposal is pinned to the current revision and is refused if the human edits the page first. Each operation is an object with an "op" field: {"op":"update_text","target":ELEMENT_ID,"value":TEXT} · {"op":"rename","target":ELEMENT_ID,"name":TEXT} · {"op":"update_style","target":ELEMENT_ID,"styles":{CSS}} · {"op":"update_attrs","target":ELEMENT_ID,"attrs":{HTML_ATTRS}} · {"op":"set_visible","target":ELEMENT_ID,"visible":BOOL} · {"op":"move","target":ELEMENT_ID,"index":N} or {"op":"move","target":ELEMENT_ID,"parent":ELEMENT_ID,"index":N} · {"op":"add_section","sectionType":ONE_OF(header|hero|features|products|testimonials|pricing|faq|cta|contact|footer),"afterElementId":ELEMENT_ID} · {"op":"delete","target":ELEMENT_ID}

Page: /app/

Input schema

{
  "type": "object",
  "properties": {
    "summary": {
      "type": "string",
      "description": "One line stating the intent, shown to the human as the proposal title."
    },
    "operations": {
      "type": "array",
      "description": "The edits to propose, in the order they should apply.",
      "items": {
        "type": "object"
      }
    }
  },
  "required": [
    "summary",
    "operations"
  ],
  "additionalProperties": false
}