Skip to main content
Glama

List the people

list_people
Read-only

Lists everyone in the project's People (customers, subscribers, people who signed up on its site or in its app, leads, creators, press, people who wrote to its accounts or filled in a form on its ads), every one in a single answer: each with their name, kind, stage, first role and last touch, with the total and the totals by stage. To find one person and their history use crm_search and crm_timeline; their messages are inbox_read.

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": "list_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds behavioral detail the annotations do not: it returns everyone in a single answer (no paging/filtering), and it returns per-person fields plus a total and totals by stage. It does not cover result limits or ordering, which keeps it just below top marks.

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 content is front-loaded: the enumeration comes first, return shape second, alternatives last. It is dense, though, because the long parenthetical list of person types and the run-on colon chain take up more space than the rest of the definition needs.

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 read-only, single-optional-parameter list tool with no output schema, the description is nearly complete: it explains both what comes back (name, kind, stage, first role, last touch, totals by stage) and which sibling tools handle adjacent needs. It leaves out expected result volume and ordering, which matters for a tool that returns an entire project's people in one answer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter and schema coverage is 100%, so the baseline is 3. The description refers to "the project's People," which reinforces the project-scoping semantics, but it adds nothing about id-versus-name handling or the optional single-project default beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Lists everyone in the project's People") and then enumerates the entity kinds covered: customers, subscribers, site or app signups, leads, creators, press, and inbound contacts. That scope is distinct enough from crm_search and crm_timeline that an agent can pick this tool without opening another schema.

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

Usage Guidelines5/5

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

The description explicitly routes between alternatives: use crm_search and crm_timeline to find one person and their history, and use inbox_read for messages. It also implies this is the bulk-enumeration choice ("every one in a single answer"), so the when-to-use versus when-not-to-use split is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.