Skip to main content
Glama

persons_list_all_auto

Fetch all persons with automatic pagination. Apply filters by owner, organization, or name to get the complete list without manual management.

Instructions

Automatically fetch ALL persons using pagination.

This tool handles pagination automatically and returns all persons matching the filters. Use this when you need the complete list without managing pagination manually.

Warning: This can return a large dataset if you have many persons.

Supports the same filters as persons_list:

  • user_id: Filter by owner

  • org_id: Filter by organization

  • first_char: Filter by first character of name

  • filter_id: Apply a saved filter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNoFilter by owner user ID
org_idNoFilter by organization ID
first_charNoFilter by first character of name (e.g., "A", "B")
filter_idNoFilter ID to apply
sortNoField to sort by (e.g., "name", "email")
Behavior4/5

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

Discloses automatic pagination, returns all matching persons, and warns about large datasets. With no annotations, this sufficiently covers key behaviors, though rate limits or timeout info is missing.

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?

Clear and well-structured with bullets. Could combine first two sentences but overall efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequately covers pagination and filters, but lacks output format details or default sorting. Given no output schema, some aspects are left implicit.

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?

All parameters are already documented in input schema (100% coverage). Description merely repeats filters, adding no new semantic meaning beyond grouping as 'same filters as persons_list'.

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?

Clearly states it fetches ALL persons with automatic pagination, distinguishing it from manual pagination tools like persons_list. Verb and resource are specific.

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

Usage Guidelines4/5

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

Explicitly advises using when complete list is needed without manual pagination. Implicitly contrasts with persons_list, but lacks explicit 'when not to use' guidance.

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