Skip to main content
Glama

leads_list_all_auto

Fetch all non-archived leads automatically with pagination handling. Returns complete results in one response using the same filters as the list tool. Ideal for exports and reports.

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
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
max_itemsNoMaximum number of items to return
Behavior4/5

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

While no annotations are provided, the description discloses key behaviors: automatic pagination handling, returning all non-archived leads, sorting by creation time, and potential for large datasets. It also warns about large data and suggests using filters. However, it does not mention authentication requirements or rate limits, but these may be assumed from context.

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 description is relatively long but well-structured with a bold warning, bulleted workflow tips, and common use cases. Every sentence adds value, though it could be slightly more concise. The front-loading of the main purpose is effective.

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?

Given the tool's complexity and lack of output schema, the description covers filters, pagination behavior, sorting, and use cases. It does not describe the exact return format, but the warning about large datasets and the mention of single response provide enough context for selection. Slightly more detail on return structure could improve completeness.

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%, so the baseline is 3. The description adds value by stating that filters are the same as 'leads/list', explaining that no start/limit management is needed, and providing examples of how to use max_items. This clarifies parameter usage beyond the 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 the tool fetches ALL leads with automatic pagination, returning all results in a single response. It distinguishes itself from 'leads/list' by highlighting automatic pagination vs manual pagination, and explicitly mentions that it returns non-archived leads.

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 states when to use this tool (for comprehensive exports/reports/analysis) and contrasts it with 'leads/list' (manual pagination). It provides workflow tips including using filters to limit results and specifying max_items. Common use cases are given with concrete filter examples.

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