Skip to main content
Glama
webflow

Webflow

Official
by webflow

Ask Webflow AI

ask_webflow_ai

Get answers about Webflow API functionality and usage directly from AI assistance. Ask questions to understand how to interact with Webflow sites, pages, and collections through the API.

Instructions

Ask Webflow AI about anything related to Webflow API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes

Implementation Reference

  • Registers the "ask_webflow_ai" MCP tool, defining its schema, description, and inline handler function that calls postChat and formats the response.
    export function registerAiChatTools(server: McpServer) {
      server.registerTool(
        "ask_webflow_ai",
        {
          title: "Ask Webflow AI",
          description: "Ask Webflow AI about anything related to Webflow API.",
          inputSchema: z.object({ message: z.string() }),
        },
        async ({ message }) => {
          const result = await postChat(message);
          return {
            content: [{ type: "text", text: result }],
          };
        }
      );
    }
  • Core helper function that performs the HTTP POST request to Webflow's AI chat API endpoint, constructs the request body, and streams the response via streamToString.
    async function postChat(message: string) {
      const response = await fetch(`${BASE_URL}/api/fern-docs/search/v2/chat`, {
        method: "POST",
        headers: {
          "content-type": "application/json",
          "x-fern-host": X_FERN_HOST,
        },
        body: JSON.stringify({
          messages: [{ role: "user", parts: [{ type: "text", text: message }] }],
          conversationId: randomUUID(),
          url: BASE_URL,
          source: "mcp",
        }),
      });
    
      const result = await streamToString(response);
      return result;
    }
  • Utility function to convert a streaming Fetch Response body into a complete string by reading chunks with TextDecoder.
    async function streamToString(response: Response) {
      const reader = response.body?.getReader();
      if (!reader) {
        throw new Error("!reader");
      }
    
      let result = "";
      while (true) {
        const { done, value } = await reader.read();
        if (done) break;
    
        // Convert the Uint8Array to a string and append
        result += new TextDecoder().decode(value);
      }
    
      return result;
    }
  • src/mcp.ts:48-48 (registration)
    Calls registerAiChatTools to include the ask_webflow_ai tool in the main MCP server registration.
    registerAiChatTools(server);
  • Zod input schema for the tool: requires a 'message' string.
    inputSchema: z.object({ message: z.string() }),
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to describe key traits: whether it's read-only or has side effects, authentication needs, rate limits, response format, or how the AI processes queries. The phrase 'ask about anything' is overly broad and doesn't set realistic expectations, leaving critical behavior unspecified.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's function. It's front-loaded with the core action ('Ask Webflow AI') and avoids unnecessary words. Every part of the sentence contributes to the basic purpose, making it appropriately concise.

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 tool's complexity (AI-based querying with undefined behavior), lack of annotations, no output schema, and poor parameter documentation, the description is incomplete. It doesn't explain what the tool returns, how to interpret results, or any limitations, leaving significant gaps for effective agent use in a context with many specialized sibling tools.

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

Parameters2/5

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

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic information. The description doesn't mention the 'message' parameter at all, offering no guidance on its content, format, or examples. This leaves the parameter's purpose and usage completely undocumented, failing to compensate for the schema gap.

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 'Ask Webflow AI about anything related to Webflow API' which provides a general purpose (querying an AI about Webflow API topics). However, it's vague about what 'ask' entails (e.g., is it conversational, does it generate code, provide explanations?) and doesn't distinguish it from sibling tools like 'webflow_guide_tool' or 'de_learn_more_about_styles' that might also provide information. It's not tautological but lacks specificity.

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?

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context (e.g., use for API troubleshooting vs. general learning), or exclusions. With many sibling tools for specific Webflow operations, users are left guessing when this AI query tool is appropriate.

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