Skip to main content
Glama
webflow

Webflow

Official
by webflow

Ask Webflow AI

ask_webflow_ai
Read-only

Ask questions about the Webflow API and receive direct answers from the AI.

Instructions

Ask Webflow AI about anything related to Webflow API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesThe message to ask Webflow AI about.

Implementation Reference

  • The registerAiChatTools function registers the 'ask_webflow_ai' tool with the MCP server. The handler (line 22-27) receives the 'message' input, calls postChat(), and returns the result as text content.
    export function registerAiChatTools(server: McpServer) {
      server.registerTool(
        "ask_webflow_ai",
        {
          description: "Ask Webflow AI about anything related to Webflow API.",
          title: "Ask Webflow AI",
          annotations: {
            openWorldHint: true,
            readOnlyHint: true,
          },
          inputSchema: {
            message: z.string().describe("The message to ask Webflow AI about."),
          },
        },
        async ({ message }) => {
          const result = await postChat(message);
          return {
            content: [{ type: "text", text: result }],
          };
        }
      );
    }
  • Input schema definition for the 'ask_webflow_ai' tool. It defines a single string 'message' parameter described as 'The message to ask Webflow AI about.' Also includes title, description, and annotations (openWorldHint, readOnlyHint).
    {
      description: "Ask Webflow AI about anything related to Webflow API.",
      title: "Ask Webflow AI",
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
      },
      inputSchema: {
        message: z.string().describe("The message to ask Webflow AI about."),
      },
  • src/mcp.ts:48-53 (registration)
    The registerTools function in src/mcp.ts calls registerAiChatTools(server) at line 53, which registers the 'ask_webflow_ai' tool on the MCP server.
    export function registerTools(
      server: McpServer,
      getClient: () => WebflowClient,
      getAccessToken: () => string,
    ) {
      registerAiChatTools(server);
  • The postChat helper function sends a POST request to the Webflow SDK chat endpoint with the user's message, returning the streamed response as a string.
    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;
    }
  • The streamToString helper function reads a Response body stream and concatenates chunks into a single string using 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;
    }
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds no additional behavioral context beyond these annotations, which is acceptable but does not enhance transparency.

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 is front-loaded and contains no redundant information, making it highly concise.

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

Completeness4/5

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

The description is sufficient for a simple Q&A tool with one parameter and annotations. It could mention the nature of the AI response, but the current text is adequate given the tool's simplicity.

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?

The input schema covers the single parameter with a clear description. The tool description adds no extra semantic meaning beyond what the schema provides, earning the baseline score.

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

Purpose5/5

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

The description clearly states the verb 'ask' and the resource 'Webflow AI', specifying the scope 'anything related to Webflow API'. It effectively distinguishes this Q&A tool from sibling tools that focus on specific functionalities.

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

Usage Guidelines3/5

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

The description implies use for asking questions about Webflow API but does not explicitly state when to use this tool versus alternatives, nor does it provide when-not guidance.

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