Skip to main content
Glama

leads_list

List leads with pagination and filtering by owner, person, organization, or custom filter. Sorted by creation time.

Instructions

List leads with pagination and filtering options.

Returns a paginated list of non-archived leads. Use filters to narrow results by owner, person, or organization.

Workflow tips:

  • Leads are sorted by creation time (oldest to newest)

  • Use owner_id to filter by lead owner

  • Use person_id or organization_id to filter by associated entities

  • filter_id takes precedence over other filters

  • Use start/limit for pagination (default limit: 100, max: 500)

  • For all leads without pagination, use leads/list_all_auto instead

  • Leads inherit custom fields structure from deals

Common use cases:

  • List all leads: {}

  • List leads for a specific owner: { "owner_id": 123 }

  • List leads for a person: { "person_id": 456 }

  • List leads for an organization: { "organization_id": 789 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
owner_idNoFilter by owner (user) ID
person_idNoFilter by person ID
organization_idNoFilter by organization ID
filter_idNoID of the filter to use
sortNoField names and sorting mode (e.g., "title ASC, value DESC")
startNoPagination start
limitNoNumber of items to return
Behavior5/5

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

No annotations provided; description fully compensates by disclosing behavioral details: lists non-archived leads, sorted oldest to newest, pagination defaults, filter_id precedence, custom fields inheritance from deals.

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

Conciseness5/5

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

Well-structured with one-line summary, detailed sections, workflow tips, and common use cases. Every sentence adds value; not verbose.

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?

Given 7 optional parameters, filtering, pagination, and no output schema, description is complete: covers pagination, filtering, sorting, precedence, custom fields, and implies return of paginated leads.

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

Parameters5/5

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

Schema coverage is 100%, but description adds semantic meaning beyond schema: explains relationships (e.g., owner_id filters by lead owner), precedence of filter_id, and provides concrete examples.

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?

Description clearly states 'List leads with pagination and filtering options' and distinguishes from siblings like 'leads_list_all_auto' by specifying non-archived leads and pagination.

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?

Provides explicit workflow tips, filter precedence, and alternative when not to use this tool (leads_list_all_auto for all leads without pagination). Common use cases illustrate typical inputs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iamsamuelfraga/mcp-pipedrive'

If you have feedback or need assistance with the MCP directory API, please join our Discord server