Skip to main content
Glama
deenesjakoruzh
webflow

Webflow

Official
by webflow
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get Designer App Connection Info

get_designer_app_connection_info

Retrieve connection details for the Webflow Designer App to enable API access and manage site integrations.

Instructions

Get Webflow MCP App Connection Info. if user ask to get Webflow MCP app connection info, use this tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/localDeMCPConnection.ts:14-29 (registration)
    Registers the 'get_designer_app_connection_info' tool. Includes inline schema (empty object) and handler that delegates to an internal RPC call for 'local_de_mcp_connection_tool' via formatResponse.
    server.registerTool(
  "get_designer_app_connection_info",
  {
    title: "Get Designer App Connection Info",
    description:
      "Get Webflow MCP App Connection Info. if user ask to get Webflow MCP app connection info, use this tool",
    inputSchema: z.object({}),
  },
  async () => {
    try {
      return formatResponse(await localDeMCPConnectionToolRPCCall());
    } catch (error) {
      return formatErrorResponse(error);
    }
  }
);
  • src/tools/localDeMCPConnection.ts:22-28 (handler)
    Handler function for the tool, which calls the RPC tool and formats the response.
    async () => {
  try {
    return formatResponse(await localDeMCPConnectionToolRPCCall());
  } catch (error) {
    return formatErrorResponse(error);
  }
}
  • src/tools/localDeMCPConnection.ts:20-20 (schema)
    Input schema for the tool (empty object).
    inputSchema: z.object({}),

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read operation ('Get'), but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or what the output contains. This leaves gaps in understanding how the tool behaves.

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

Conciseness3/5

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

The description is two sentences but includes redundant phrasing ('Get Webflow MCP App Connection Info' repeated) and the second sentence is overly simplistic ('if user ask...'). It could be more streamlined, though it's not excessively verbose.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'Connection Info' returns (e.g., data format, structure) or address potential complexities like error cases. For a tool that likely involves authentication details, more context is needed.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate here. Baseline is 4 as it adequately handles the zero-param case without redundancy.

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 'Get Webflow MCP App Connection Info' with the verb 'Get', which clarifies it retrieves information. However, it doesn't specify what 'Connection Info' entails (e.g., tokens, URLs, status) or differentiate it from sibling tools like 'sites_get' or 'collections_get', making it somewhat vague.

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 includes a conditional statement 'if user ask to get Webflow MCP app connection info, use this tool', which provides basic usage context but lacks explicit guidance on when to use alternatives, prerequisites, or exclusions. No sibling tools are mentioned for comparison.

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