Skip to main content
Glama

deals_list

Retrieve paginated lists of deals with filters for status, stage, owner, person, or organization.

Instructions

List deals with pagination and filtering options.

Returns a paginated list of deals. Use filters to narrow results by status, stage, owner, person, organization, or pipeline.

Workflow tips:

  • Use status filter to get only 'open', 'won', 'lost', or 'all_not_deleted' deals

  • Set owned_by_you=1 to see only your deals

  • Combine with filter_id to use pre-configured Pipedrive filters

  • Use start/limit for pagination (default limit: 100, max: 500)

  • For all deals without pagination, use deals/list_all_auto instead

Common use cases:

  • List all open deals: { "status": "open" }

  • List my won deals: { "status": "won", "owned_by_you": 1 }

  • List deals in a specific stage: { "stage_id": 123 }

  • List deals for a person: { "person_id": 456 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by deal status
stage_idNoFilter by stage ID
user_idNoFilter by user (owner) ID
person_idNoFilter by person ID
org_idNoFilter by organization ID
pipeline_idNoFilter by pipeline ID
filter_idNoID of the filter to use
sortNoField to sort by (e.g., title, value, stage_id)
sort_byNoSort direction
owned_by_youNoFilter deals owned by the authorized user (1 = yes, 0 = no)
startNoPagination start
limitNoNumber of items to return
Behavior4/5

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

No annotations provided, but the description explains pagination limits (default 100, max 500) and filtering capabilities. It implies read-only behavior but does not explicitly state idempotency or auth requirements, which is acceptable given the context.

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?

The description is well-structured with sections for purpose, workflow tips, and common use cases. It is concise yet informative, with no unnecessary words.

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 has 12 parameters and no output schema, the description covers pagination, filtering, and common use cases adequately. It lacks details about return format but that is acceptable since no output schema is provided.

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 description coverage is 100%, so baseline is 3. The description adds usage patterns and examples (e.g., 'status': 'open') but does not provide deeper semantics beyond what the schema already includes.

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 lists deals with pagination and filtering options. It differentiates from siblings like deals_search and deals_list_all_auto by specifying the paginated nature and mentioning alternatives.

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 guidance on when to use filters, pagination, and workflow tips. It also mentions the alternative deals/list_all_auto for unpaginated results, helping the agent choose correctly.

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