MCP server no longer exposing element-edit and CMS tools (data_element_tool, data_cms_tool)

Over the past sessions the Webflow MCP server has been serving my client a bundle that includes the create-only builders (Element Builder, WHTML Builder, Component Builder) plus Style, Sites, Forms, Localization, Sitemap, Comments, Assets, and the Designer bridge — but not the tools that read a CMS collection's fields or read/edit/delete existing elements (e.g. data_element_tool, data_cms_tool, data_pages_tool).

Earlier work on the same site clearly ran on those tools, so something changed in what the server hands out. I'd like to understand whether this is intended, a staged rollout, or a bug.

What I'm seeing

• The tool bundle I receive contains only: Element Builder, WHTML Builder, Component Builder, Style Tool, Data Sites Tool, Data Forms Tool, Data Localization Tool, Data Sitemap Indexing Tool, Data Comments Tool, Data Webhook Tool, Designer Asset Tool, Element Snapshot Tool, Designer Tool, Ask Webflow AI, Webflow Guide Tool, Get More Tools, plus a couple of enterprise/agent/fonts tools.

• There is no tool to:

  • list a CMS collection's fields / get a collection schema (i.e. no list_collections / get_collection)

  • read the existing element tree, or update/remove an element that already exists

• The builders' own input schemas still reference the missing tools by name. For example, the CMS binding on the Element Builder says the field_id should be discovered "with data_cms_tool > get_collection" — but data_cms_tool is not in the served bundle.

• Calling the get_more_tools discovery endpoint for both the ELEMENTS and CMS categories returns: "we have shown you the full tool list."

Concrete impact

I'm finishing a CMS Collection template page. The hero paragraph's copy is already correct; it just needs the collection's First Name field bound inline. The Element Builder supports CMS bindings via source_type: "cms", but that requires a field_id, and nothing in the served bundle can read the collection to obtain it. So the binding can't be created programmatically — even though the exact same kind of work succeeded in earlier sessions.

Questions

1. Was the served MCP tool bundle changed recently to remove element-read/edit and CMS-schema tools? If so, is it intended or a staged rollout?

2. If those tools still exist, what determines whether a given session/connector receives them? (Is there a scope, connector version, or account setting involved?)

3. What's the supported way today to obtain a CMS collection's field_id values for use in an Element Builder CMS binding, if data_cms_tool/get_collection isn't served?

4. If the builder schemas reference data_cms_tool/data_element_tool, should those be considered part of the intended surface — i.e. is their absence a bug?

Environment

• Client: Claude (MCP)

• Connector: Webflow (connected, all 20 tools enabled in tool permissions)

• Site ID: 6757f5422d8fff8f73671c7c

• Last MCP changelog entry I can find: v1.3 (May 21) — added element query/add/reposition/delete tools; nothing removed since.

Any clarification appreciated — thanks!