123FormBuilder MCP Server and API by Cotlet

Add form field in 123FormBuilder

123formbuilder_add_form_field

Read-onlyIdempotent

Add form field in the user's own 123FormBuilder account from ChatGPT, Claude or any AI agent. Returns how to do it in 123FormBuilder step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's 123FormBuilder Cloud Browser. 123FormBuilder's official API: 123FormBuilder has a REST API v2 with token login (checked 23 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "123formbuilder_add_form_field"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The description explicitly discloses that the tool 'opens nothing by itself', which aligns with readOnlyHint=true and destructiveHint=false. The added API v2/token-login note is not clearly tied to this tool's behavior and could confuse, but the key side-effect boundary is stated.

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 core instruction is front-loaded, but the description includes unnecessary audience labels ('ChatGPT, Claude or any AI agent') and an API note that does not help an agent invoke this specific guide tool. Those sentences add noise without improving selection or invocation.

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?

For a zero-parameter, read-only guidance tool with no output schema, the description explains the content returned and the follow-up browser tool path. It does not specify whether the steps are static or account-specific, but the definition is sufficient for correct use.

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 tool takes zero parameters, so there are no parameter semantics for the description to clarify. Baseline 4 applies.

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

Purpose4/5

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

The description explains that the tool returns step-by-step instructions (screens, buttons, fields) and explicitly says it opens nothing by itself, routing actual changes to the cotlet_browser_* tools. However, the opening phrase 'Add form field' and the title imply a mutating action, so the true read-only guidance purpose emerges only after the clarification.

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

Usage Guidelines4/5

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

It clearly says to use this tool to get the how-to and then perform the action with cotlet_browser_* tools. It does not explicitly name the other 123FormBuilder API tools as alternatives or state when not to use it, but the intended workflow is unambiguous.

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

All 123FormBuilder MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?