Supermove MCP Server and API by Cotlet

List leads in Supermove

supermove_list_leads

Read-onlyIdempotent

List leads in the user's own Supermove account from ChatGPT, Claude or any AI agent. Returns how to do it in Supermove step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Supermove Cloud Browser. Supermove's official API: Supermove has a Developer API, but it brings data in: a New Lead endpoint, a Standard Website endpoint, Add Survey and Update Project, all on a URL unique to your company (checked 28 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": "supermove_list_leads"
  }
}

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?

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the tool 'opens nothing by itself' and returns screens, buttons, and fields rather than performing the action. It does not mention permissions, freshness of the guide, or failure modes, which keeps it short of 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?

The purpose and the hand-off to browser tools are front-loaded, which is good. The closing sentence about Supermove's Developer API is long, tangentially argued, and contains a confusing date reference ('checked 28 Oct 2026'); it justifies the browser approach but could be trimmed substantially.

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?

With zero parameters, no output schema, and read-only annotations, the definition covers what an agent needs: what it returns (step-by-step instructions) and what to do next (browser tools). It is slightly incomplete on how this relates to the generic 'cotlet_app_guide' sibling, but otherwise sufficient.

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 baseline is 4. There is nothing parameter-related for the description to compensate for, and it correctly does not invent inputs.

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 first sentence names a specific verb and resource ('List leads in the user's own Supermove account'), and the description immediately clarifies the real behavior: it returns a step-by-step how-to rather than lead data. That disclosure is good, but the mismatch between the name ('list_leads') and the actual output (instructions) means an agent must read past the opening to understand what it truly does.

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?

The description states a clear follow-on workflow: use this to get the steps, then execute them with 'cotlet_browser_*' tools in the Supermove Cloud Browser. What is missing is explicit routing against the close sibling 'cotlet_app_guide' or any when-not-to-use condition, so the agent is not told why this app-specific guide beats the generic one.

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

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