Skip to main content
Glama

leads_list

List leads with pagination and filtering by owner, person, or organization. Use start/limit for pagination and optional date or filter ID restrictions.

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

  • Use add_time_from / add_time_until to filter by creation date (client-side). NOTE: this only filters the current page; for complete date-range results use leads/list_all_auto

  • 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
sortNoField names and sorting mode (e.g., "title ASC, value DESC")
limitNoNumber of items to return
startNoPagination start
owner_idNoFilter by owner (user) ID
filter_idNoID of the filter to use
person_idNoFilter by person ID
add_time_fromNoFilter leads created on or after this date (YYYY-MM-DD). Applied client-side.
add_time_untilNoFilter leads created on or before this date (YYYY-MM-DD). Applied client-side.
organization_idNoFilter by organization ID
Behavior5/5

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

Despite no annotations, the description discloses key behaviors: returns non-archived leads only, sorted oldest to newest, pagination defaults, filter precedence, client-side date filtering (only current page), custom fields inheritance. Comprehensive for a list tool.

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 sections 'Workflow tips' and 'Common use cases.' Every sentence adds value. No redundancy or wasted words. Concise yet comprehensive.

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 no output schema, the description adequately explains the return: a paginated list of non-archived leads. Covers all parameters, sorting, pagination, and caveats. Complete for a complex list tool.

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 significant context: filter_id takes precedence, add_time_from/until are client-side and page-limited, default limit 100 max 500, custom fields inherited from deals. Adds meaning beyond schema descriptions.

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?

The description clearly states the tool's purpose: 'List leads with pagination and filtering options.' It specifies it returns non-archived leads, sorted by creation time, and provides common use cases. Distinguishes from siblings like leads_list_all_auto and leads_list_archived.

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: when to use filters, pagination limits, filter_id precedence, client-side date filtering limitations, and alternative tool leads_list_all_auto for full date-range results. Covers when-not-to-use as well.

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/nubiia-dev/mcp-pipedrive'

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