Bloom MCP Server and API by Cotlet

Create lead in Bloom

bloom_create_lead

Read-onlyIdempotent

Create lead in the user's own Bloom account from ChatGPT, Claude or any AI agent. Returns how to do it in Bloom step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Bloom Cloud Browser. Bloom's official API: Bloom publishes no public API or developer docs; its only connection is a Zapier app with triggers such as new lead or new payment (checked 8 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": "bloom_create_lead"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, and the description explains exactly why: 'opens nothing by itself' — the tool returns instructions and performs no mutation. It also discloses the integration reality (no public API, Zapier-only triggers), which is genuinely useful context an agent cannot get from structured fields, though it omits anything about response size or limits.

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?

Purpose is front-loaded and the crucial 'these are instructions, not an action' clarification follows immediately. The trailing API/Zapier sentence is tangential and the 'checked 8 Nov 2026' date is noise, but the rest is dense and waste-free.

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

Completeness5/5

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

With no input or output schema, the description must carry everything, and it does: what the call returns (screens, buttons, fields), what it does not do (no side effects), and what to do next (browser tools). An agent can act correctly on this alone.

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 the baseline is 4 and there is nothing for the description to disambiguate. No parameter detail is needed or missing.

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 a specific verb and resource ('Create lead in the user's own Bloom account') and immediately clarifies the twist that it returns step-by-step instructions rather than performing the action. It distinguishes itself from the browser siblings by naming them as the follow-up mechanism, though it never contrasts itself with bloom_create_project or the other bloom_* guide tools.

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 an explicit usage sequence: call this to get the click-by-click steps, then execute them via cotlet_browser_* in the Bloom Cloud Browser. It does not state any when-not-to-use condition or compare against cotlet_app_guide / sibling bloom_* tools, which keeps it short of a 5.

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

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