Skill Migration
The Webflow MCP server has updated several tool and action names across releases. If a skill, prompt, or automation still refers to a name from an older version, that call may fail once the action has moved or been renamed.
This guide lists every tool and action name that changed across v1.3, v2.0, and v2.0.1, so you can update older references to the names the current version expects. A “skill” here means any saved set of instructions that tells an agent how to work with Webflow, together with the specific tool calls it relies on.
It is written for two readers: developers updating skills or automations they wrote against an earlier version, and agents pointed at this page to update those skills on their own. After reading it, you should be able to find every earlier tool or action reference in a skill, replace it with the current name, and recognize the two cases where renaming alone is not enough to keep the skill working.
How to use this with an agent
Point an agent at this page and ask it to update a skill. The tables in this guide list only the names that changed, so they are the reference to work from. Any tool or action not listed here kept its name and needs no change, which means an agent can leave unlisted calls untouched.
Work through a skill in this order:
- Find every Webflow tool and action name the skill refers to.
- Look each one up in the tables below. If it appears in an “earlier” column, replace it with the current name.
- Watch for relocations. An action can keep its name but move to a different tool, so the tool named in the call has to change even when the action name stays the same.
- Check the behavioral changes near the end. Some updates affect how a skill runs, not just what it is called, and a find-and-replace pass alone will not catch them.
Record the version each skill was built against
When you create or update a skill, record which Webflow MCP version it was built against, somewhere durable in the skill itself. The next time the server changes, that note tells you, or an agent, exactly which part of a guide like this one to apply, turning the update into a lookup rather than a guess about what the skill was written for.
The whole of this guide is organized around that one question. A skill built against v2.0.1 needs no changes today, a skill built against v2.0 needs only a few, and a skill built against v1.3 needs the most. Without a recorded version, working that out means inspecting the tool and action names the skill calls and inferring the version from them, which is slower and less certain. With it, you go straight to the matching section.
Record it in whatever form fits how you keep skills. What matters is that the version is written down, stays with the skill, and is easy to find later. The exact wording and location are up to you.
v1.3 to v2.0 changes
v2.0 was a major release. Nearly all of the tools that previously required a Designer session via the Webflow MCP Bridge app were rebuilt to run without it. These rebuilt tools are headless, meaning they work directly through Webflow’s Data API and an agent can call them from a server or script with no Designer session open. As part of that work, several tools gained a data_ prefix, a few actions were renamed, and everything to do with a Designer session like selecting elements or moving around the canvas was gathered into a single new tool called designer_tool.
Tools renamed, actions unchanged
These tools gained the data_ prefix and became headless. Only the tool name changed; every action name inside them stayed the same.
Tools that split into more than one tool
Several v1.3 tools were broken apart. The work that could run without the Designer moved into a data_ tool, and anything that acts on the live canvas moved into the new designer_tool.
Actions moved into designer_tool
These actions kept their names but moved out of their v1.3 tool and into designer_tool. Update the tool named in the call, even though the action name is the same.
Actions renamed
One action replaced by several
The old single call that returned assets and folders together no longer exists. Use the separate data_assets_tool actions instead.
Renamed and given a different input
This one changes more than the name, so a find-and-replace pass alone will produce a call that fails.
Unchanged in this release
These tools kept both their names and their existing action names. Some gained new actions, but nothing was renamed: data_sites_tool, data_pages_tool, data_cms_tool, data_comments_tool, data_scripts_tool, data_webhook_tool, data_localization_tool, data_enterprise_tool, element_snapshot_tool, ask_webflow_ai, webflow_guide_tool, and get_more_tools. New tools also appeared (data_analyze_tool, data_sitemap_tool, data_fonts_tool, data_forms_tool, and data_agent_instructions_tool), but new tools do not affect skills written against the earlier version.
v2.0 to v2.0.1 changes
v2.0.1 was a minor release. No tools were renamed and nothing became headless that was not already. Instead, two of the larger tools were split so that related actions live in their own focused tools. In every split below the action names stayed the same; only the tool that holds them changed, so these are relocations to update rather than renames.
data_element_tool split
Element settings and data bindings moved out of data_element_tool into a new tool, data_element_settings_tool. A binding is a link from an element to a data source, such as a content field, so the element shows that data instead of a fixed value.
Everything else in data_element_tool stayed where it was, including the attribute actions get_attributes, set_attributes, and remove_attribute.
data_component_tool split
Props and variants moved out of data_component_tool into two new tools. A prop is a configurable input on a component, and a variant is a saved alternate version of a component, such as a different size or state.
The remaining data_component_tool actions stayed put: getting and querying components, creating a blank component, duplicating, transforming an element into a component, inserting and unlinking instances, updating metadata, and unregistering a component.
Consolidated old-to-current lookup
Use this section to update a skill in a single pass, whichever version it was written against. It lists only names that changed, and where an action moved twice (from v1.3 to v2.0 and again to v2.0.1) it shows the final v2.0.1 destination directly, so you do not have to trace it through the middle release. Anything not listed here kept its name.
Tools
Actions from tools that split, coming from v1.3
element_tool. Most editing actions kept their names under data_element_tool. The exceptions are below.
de_component_tool. Core component actions kept their names under data_component_tool. The exceptions are below.
de_page_tool. Only create_page moved to data_pages_tool. Everything else moved to designer_tool with the same action names: create_page_folder, get_current_page, get_current_mode, get_current_branch_id, get_branch_parent_page_id, switch_page, and list_branches.
asset_tool. upload_image_by_url stayed in asset_tool and still requires a Designer session through the Bridge app. The rest moved to data_assets_tool, as shown below.
variable_tool. The variable, collection, and mode actions moved to data_variable_tool with the same names. The four per-style variable-mode actions (get_style_variable_modes, set_style_variable_mode, remove_style_variable_mode, remove_all_style_variable_modes) moved to data_style_tool.
Actions that moved again, coming from v2.0
If a skill was written against v2.0, these are the only relocations to apply. The action names did not change; only the tool did.
Behavioral changes to check
Two of the updates change how a skill behaves, not just what a call is named. A find-and-replace pass will not catch either one, so check for both by hand after you have updated the names. These are the two cases mentioned at the start where renaming alone is not enough to keep a skill working.
The Designer session requirement changed
In v1.3, editing elements, components, styles, and variables required an open Designer session through the Webflow MCP Bridge app. From v2.0 onward, the rebuilt headless tools (the data_ tools) do this work without a session, running directly through Webflow’s Data API. If a skill opens or waits for a Designer session only so that it can edit content, that step is no longer needed and can be removed.
A few things still require a Designer session through the Bridge app: selecting an element and moving around the canvas (now in designer_tool), uploading an image by URL (asset_tool.upload_image_by_url), and capturing an element snapshot (element_snapshot_tool). A skill that relies on any of these still needs the session.
get_asset_preview takes an asset ID, not a URL
As noted in the v1.3 to v2.0 tables, the earlier get_image_preview accepted an image URL, and its replacement get_asset_preview accepts an asset ID instead. A skill that previewed an image by URL has to first look up that asset’s ID, for example with data_assets_tool.list_assets, and pass the ID. This changes what the skill has to supply, so updating the name alone will leave the call broken.
Summary at a glance
Three releases are covered here, and the amount of work to update a skill depends on which one it was written against.
Written against v1.3. Expect the most changes. v2.0 was a major release that rebuilt nearly all of the Designer-session tools to run headlessly, added the data_ prefix to many of them, renamed a few actions, and gathered element selection and canvas navigation into the new designer_tool. Several v1.3 tools were split apart, and one tool (variable_tool) was removed, its work moved to data_variable_tool and data_style_tool. Work through the v1.3 to v2.0 tables, then apply the v2.0 to v2.0.1 changes on top, or use the consolidated lookup to jump straight to the current names in one pass.
Written against v2.0. Expect only a few changes. v2.0.1 was a minor release that split element settings into data_element_settings_tool and split component props and variants into data_component_props_tool and data_component_variants_tool. The action names did not change; only the tool holding them did. The “Actions that moved again, coming from v2.0” table lists every one.
Written against v2.0.1. Nothing to change. These are the current names.
Two updates need a manual check regardless of version, because renaming alone will not fix them: the Designer session requirement (most editing no longer needs a session, though selection, canvas navigation, image upload by URL, and snapshots still do) and get_asset_preview (which now takes an asset ID rather than an image URL). Both are covered in the behavioral changes section above.
