Formstack MCP Server and API by Cotlet

Change notification recipients in Formstack

formstack_change_notification_recipients

Read-onlyIdempotent

Change notification recipients in the user's own Formstack account from ChatGPT, Claude or any AI agent. Returns how to do it in Formstack step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Formstack Cloud Browser. Formstack's official API: Formstack has a full REST API for Forms, the V2025 API released in August 2025, but it is an add-on and Formstack publishes no MCP server for it (checked 22 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": "formstack_change_notification_recipients"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that the tool opens nothing by itself and returns detailed screen/button/field instructions, and that actual changes require separate browser tools. This adds meaningful context about side effects and follow-up actions, though it does not cover rate limits or authentication.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and behavior, followed by a relevant note about the API landscape. The third sentence about Formstack's API is slightly tangential but ultimately justifies why this instructional tool exists.

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?

Given the tool's low complexity (no parameters, no output schema), the description provides sufficient context: what it returns, that it is inert, and how to complete the task. It could specify the exact output format more, but overall it is complete enough for an agent to use correctly.

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 no parameters, so the schema is trivially complete. The description appropriately does not need to explain parameter meanings, and the baseline for zero parameters 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 states the specific resource (notification recipients) and clarifies that the tool returns step-by-step instructions rather than performing the change itself. However, the opening phrase 'Change notification recipients' could initially imply a direct action, creating a slight mismatch between the name and actual behavior.

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 gives a clear workflow: first get the steps, then execute them with the cotlet_browser_* tools in the user's Formstack Cloud Browser. It also explains why this route is necessary (no MCP server for Formstack's official API), which helps the agent choose this tool over alternatives.

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

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