Method CRM MCP Server and API by Cotlet

List customers and leads in Method CRM

method_crm_list_customers_and_leads

Read-onlyIdempotent

List customers and leads in the user's own Method CRM account from ChatGPT, Claude or any AI agent. Returns how to do it in Method CRM step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Method CRM Cloud Browser. Method CRM's official API: Method CRM has a full REST API with read and write access to permitted records, but no ready-made official MCP server (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": "method_crm_list_customers_and_leads"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description reinforces this with 'opens nothing by itself'. Beyond that it discloses the return payload (screens, buttons, fields) and the API/MCP availability status, which the annotations do not cover. It omits prerequisites such as the user needing a connected Method CRM browser session.

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 behavioral disclosure sits in the second sentence rather than being front-loaded, and 'from ChatGPT, Claude or any AI agent' is marketing filler that does not help selection. The parenthetical API audit note with a checked date is tangential to invoking the tool.

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 helper with no output schema, the description supplies what is missing structurally: what is returned and which tools to use next. It leaves out preconditions like having an authenticated Method CRM session in the cloud browser, which keeps it from a 5.

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; there is nothing for the description to disambiguate. The schema's empty object with additionalProperties false is consistent with the stated no-input nature.

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 resource (customers and leads in the user's own Method CRM account) and specifies the actual output: step-by-step instructions with screens, buttons, and fields. The headline verb 'List' is slightly at odds with the disclosed behavior of returning guidance rather than records, but the second sentence resolves it. No sibling tool is named for contrast, so it stops short of a 5.

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

Usage Guidelines3/5

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

It gives a clear follow-on path: use the cotlet_browser_* tools in the user's Method CRM Cloud Browser after reading the steps. However, it offers no when-not-to-use guidance and never contrasts itself with general helpers like cotlet_app_guide or the other method_crm_* tools, so the agent must infer the boundary.

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

All Method CRM 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?