ManyChat MCP Server and API by Cotlet

Set custom field in ManyChat

manychat_set_custom_field

Read-onlyIdempotent

Set custom field in the user's own ManyChat account from ChatGPT, Claude or any AI agent. Returns how to do it in ManyChat step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ManyChat Cloud Browser. ManyChat's official API: Yes, but only on the Pro plan or higher, and it is narrow (checked 5 Nov 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": "manychat_set_custom_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?

Beyond readOnlyHint and idempotentHint, it discloses that the tool opens nothing by itself, returns screen/button/field steps, and requires subsequent browser automation. It also surfaces the official API plan limitation. It does not discuss auth or failure modes, so it is not a 5.

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?

Three sentences, but the opening "Set custom field" conflicts with the later clarification that it only returns instructions, forcing the reader to revise their model. The API caveat is useful but placed after execution details; front-loading the non-executing nature would be clearer.

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, it covers what is returned and the next tool family to use. It omits prerequisites like having a ManyChat Cloud Browser session ready, but that is a minor gap.

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 has zero parameters and the schema is empty, so there is no parameter meaning to add. Baseline for 0 params is 4.

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 names the specific resource (custom field) and account, then explicitly says it returns step-by-step instructions rather than performing the change. The name/title verb "Set" is slightly misleading, but the body corrects it; sibling differentiation is limited but not essential for this helper.

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 tells the agent to use this for how-to guidance and then execute via the cotlet_browser_* tools in the ManyChat Cloud Browser, and it notes the official API exists only on Pro+ and is narrow. It does not enumerate when to choose other manychat_* tools, but the execution handoff is explicit.

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

All ManyChat 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?