Skip to main content
Glama
webflow

Webflow

Official
by webflow

Designer Asset Tool

asset_tool

Manage Webflow site assets and folders by creating folders, retrieving all assets and folders, and updating asset details.

Instructions

Designer Tool - Asset tool to perform actions like create folder, get all assets and folders, update assets and folders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesThe ID of the site. DO NOT ASSUME site id. ALWAYS ask user for site id if not already provided or known. use sites_list tool to fetch all sites and then ask user to select one of them.
actionsYes

Implementation Reference

  • Handler function that executes the asset_tool logic by proxying to an external RPC implementation.
    async ({ siteId, actions }) => {
      try {
        return formatResponse(await assetToolRPCCall(siteId, actions));
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Tool metadata and input validation schema for asset_tool, defining possible actions like create_folder, get_all_assets_and_folders, update_asset.
    {
      title: "Designer Asset Tool",
      description:
        "Designer Tool - Asset tool to perform actions like create folder, get all assets and folders, update assets and folders",
      inputSchema: z.object({
        ...SiteIdSchema,
        actions: z.array(
          z.object({
            create_folder: z
              .object({
                name: z.string().describe("The name of the folder to create"),
                parent_folder_id: z
                  .string()
                  .optional()
                  .describe(
                    "The id of the parent folder to move the folder to."
                  ),
              })
              .optional()
              .describe("Create a folder on the site"),
            get_all_assets_and_folders: z
              .object({
                query: z
                  .enum(["all", "folders", "assets"])
                  .describe("Query to get all assets and folders on the site"),
                filter_assets_by_ids: z
                  .array(z.string())
                  .describe("Filter assets by ids")
                  .optional(),
              })
              .optional()
              .describe("Get all assets and folders on the site"),
            update_asset: z
              .object({
                asset_id: z.string().describe("The id of the asset to update"),
                name: z
                  .string()
                  .optional()
                  .describe("The name of the asset to update"),
                alt_text: z
                  .string()
                  .optional()
                  .describe("The alt text of the asset to update"),
                parent_folder_id: z
                  .string()
                  .optional()
                  .describe(
                    "The id of the parent folder to move the asset to."
                  ),
              })
              .optional()
              .describe("Update an asset on the site"),
          })
        ),
      }),
    },
  • Direct registration of the asset_tool on the McpServer instance.
    server.registerTool(
      "asset_tool",
      {
        title: "Designer Asset Tool",
        description:
          "Designer Tool - Asset tool to perform actions like create folder, get all assets and folders, update assets and folders",
        inputSchema: z.object({
          ...SiteIdSchema,
          actions: z.array(
            z.object({
              create_folder: z
                .object({
                  name: z.string().describe("The name of the folder to create"),
                  parent_folder_id: z
                    .string()
                    .optional()
                    .describe(
                      "The id of the parent folder to move the folder to."
                    ),
                })
                .optional()
                .describe("Create a folder on the site"),
              get_all_assets_and_folders: z
                .object({
                  query: z
                    .enum(["all", "folders", "assets"])
                    .describe("Query to get all assets and folders on the site"),
                  filter_assets_by_ids: z
                    .array(z.string())
                    .describe("Filter assets by ids")
                    .optional(),
                })
                .optional()
                .describe("Get all assets and folders on the site"),
              update_asset: z
                .object({
                  asset_id: z.string().describe("The id of the asset to update"),
                  name: z
                    .string()
                    .optional()
                    .describe("The name of the asset to update"),
                  alt_text: z
                    .string()
                    .optional()
                    .describe("The alt text of the asset to update"),
                  parent_folder_id: z
                    .string()
                    .optional()
                    .describe(
                      "The id of the parent folder to move the asset to."
                    ),
                })
                .optional()
                .describe("Update an asset on the site"),
            })
          ),
        }),
      },
      async ({ siteId, actions }) => {
        try {
          return formatResponse(await assetToolRPCCall(siteId, actions));
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Helper function used by the handler to invoke the RPC call for asset_tool.
    const assetToolRPCCall = async (siteId: string, actions: any) => {
      return rpc.callTool("asset_tool", {
        siteId,
        actions: actions || [],
      });
    };
  • src/mcp.ts:60-60 (registration)
    High-level registration call for designer tools, including asset_tool.
    registerDEAssetTools(server, rpc);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions actions like 'create' and 'update' which imply mutations, but doesn't disclose critical traits such as required permissions, whether changes are destructive, rate limits, or response formats. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with key actions, avoiding unnecessary words. However, it could be more structured by explicitly listing the three actions or clarifying the tool's multi-action nature upfront, but it remains efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a multi-action tool with 2 parameters (one being a complex array of actions), no annotations, no output schema, and only 50% schema coverage, the description is inadequate. It fails to explain how actions are executed, what the tool returns, or handle the nuanced behavioral aspects, making it incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%, and the description adds minimal value beyond the schema. It hints at actions like 'create folder' and 'get all assets and folders', which loosely map to the actions parameter, but doesn't explain parameter interactions, constraints, or provide additional context not already in the schema descriptions. This meets the baseline for partial coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool performs actions like 'create folder, get all assets and folders, update assets and folders', which gives a general purpose but is vague about the exact scope and lacks specificity. It doesn't clearly distinguish this multi-action tool from sibling tools that might handle similar resources (e.g., collections, pages, components), making it somewhat ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description lists actions but doesn't specify prerequisites (e.g., needing a siteId from sites_list), appropriate contexts, or exclusions, leaving the agent without clear usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/webflow/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server