Skip to main content
Glama

leads_list_all_auto

Retrieve all non-archived leads matching filters with automatic pagination. Returns complete results in a single response for exports or analysis.

Instructions

Automatically fetch ALL leads with pagination handling.

This tool automatically handles pagination and fetches all non-archived leads matching the filters. Unlike leads/list, this returns ALL results in a single response.

WARNING: This can return large datasets. Use filters to limit results.

Workflow tips:

  • Same filters as leads/list (owner_id, person_id, organization_id, filter_id)

  • Specify max_items to limit total results if needed

  • No need to manage start/limit - pagination is automatic

  • Best for exports, reports, or comprehensive analysis

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

Common use cases:

  • Get all leads: {}

  • Export all leads for a user: { "owner_id": 123 }

  • Get all leads for analysis: { "max_items": 1000 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoField names and sorting mode
owner_idNoFilter by owner (user) ID
filter_idNoID of the filter to use
max_itemsNoMaximum number of items to return
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
Behavior4/5

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

With no annotations, the description carries full burden. It discloses automatic pagination, large dataset warning, sorting by creation time, and client-side date filtering. It does not discuss rate limits or auth, but covers key behavioral traits adequately.

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?

Description is well-structured with a brief intro, warning, workflow tips, and common use cases. Every sentence adds value; no redundancy. Front-loaded with the main purpose.

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?

No output schema, but description explains what to expect (list of leads, large dataset, sorted by creation time). Covers essential aspects for a list-all tool; could mention response format but not necessary.

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?

Schema coverage is 100%, but description adds value by explaining that filters are same as leads/list and that max_items limits total results. It clarifies that no start/limit management is needed, going beyond schema.

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 it fetches ALL leads with automatic pagination, specifying it returns non-archived leads matching filters. It distinguishes from leads/list by emphasizing that this returns all results in a single response.

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?

Explicitly tells when to use this tool versus alternatives (leads/list for paginated results, this for comprehensive analysis). Provides workflow tips and common use cases, giving clear guidance on when to use it.

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