Skip to main content
Glama

products_list_all_auto

Automatically retrieve all products from Pipedrive without manual pagination. Supports filters by owner, saved filter, or first character of name.

Instructions

Automatically fetch ALL products using pagination.

This tool handles pagination automatically and returns all products 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 products.

Supports the same filters as products/list:

  • user_id: Filter by owner

  • filter_id: Apply a saved filter

  • first_char: Filter by first character of name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNoFilter by owner user ID
filter_idNoFilter ID to apply
first_charNoFilter by first character of name (e.g., "A", "B")
Behavior3/5

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

No annotations provided, so description must carry full burden. Discloses automatic pagination and large dataset risk, but omits potential rate limits, authentication needs, or maximum result size.

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?

Well-structured with front-loaded purpose, then usage guidance, warning, and filter list. However, the filter list is redundant with schema descriptions and could be shortened.

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?

No output schema exists, so description should describe return format. It mentions 'returns all products matching filters' but lacks details on ordering, fields returned, or pagination behavior.

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?

Schema coverage is 100% with clear parameter descriptions. The description repeats filter names and purposes without adding meaningful detail beyond what the schema already provides.

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 products automatically via pagination. It distinguishes from sibling tools like products_list (which likely requires manual pagination) by emphasizing automatic handling.

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 says 'Use this when you need the complete list without managing pagination manually', implying when not to use. Warns about large datasets but does not name specific alternatives or exclusions.

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