Changelog

This is an overview of the changes to the Webflow APIs and related tools. To filter the list, select one or more tags.

May 5, 2026

List Assets: folder filtering and per-asset folder context

You can now scope the List Assets endpoint (GET /v2/sites/{site_id}/assets) to return assets that are in a specified folder. In the same way, the response to this endpoint includes the folder that an asset is in.

New query parameter: folderId

Pass a folder’s ObjectId to receive only assets in that folder and all of its descendant folders. When folderId is omitted, the endpoint returns all assets on the site as before.

  • Type: string (24-character hex ObjectId)
  • Required: no
  • Behavior: recursive — assets in nested subfolders are included
  • pagination.total reflects the filtered count, so paginated UIs get correct totals
$curl -H "Authorization: Bearer $WEBFLOW_TOKEN" \
>  "https://api.webflow.com/v2/sites/$SITE_ID/assets?folderId=$FOLDER_ID"

New response field: folderId

Every asset in the response to this endpoint now includes a folderId field. The value is the ObjectId of the folder the asset belongs to, or null when the asset is at the site root.

1{
2  "assets": [
3    {
4      "id": "63e5889e7fe4eafa7384cea4",
5      "displayName": "banner.png",
6      "folderId": "6390c49774a71f99f21a08eb"
7    },
8    {
9      "id": "63e5889e7fe4eafa7384cea5",
10      "displayName": "logo.svg",
11      "folderId": null
12    }
13  ]
14}

folderId appears only in the response to the GET /v2/sites/{site_id}/assets endpoint. The single-asset GET /assets/{asset_id} and PATCH /assets/{asset_id} responses are unchanged.

May 5, 2026

MCP v1.2.1 - Improved connection reliability and Gemini compatibility

Version 1.2.1 of the Webflow MCP server improves connection reliability and fixes compatibility with Gemini-based AI clients. If you are already using the MCP server, your agents and prompts automatically use this version.

Reliability

  • Fixed connection drops: The MCP server now maintains open connections during idle periods instead of dropping them. Previously, agents could lose their session mid-task and require a full reconnect after a period of inactivity. Sessions now survive idle periods without interruption.

Bug fixes

  • Gemini compatibility: Fixed an HTTP 400 error that prevented Gemini-based AI clients from using the element_builder and component_builder tools. Gemini’s strict OpenAPI 3.0 validation rejected array schemas that were missing an items type definition. Claude-based clients were unaffected.

Resources