Skip to main content
Glama

deals_list

Retrieve a paginated list of deals with filters for status, stage, owner, and more. Use to narrow results by pipeline, person, or date range.

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

  • Use add_time_from / add_time_until to filter by creation date (client-side). NOTE: this only filters the current page; for complete date-range results use deals/list_all_auto

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 added before 2023: { "add_time_until": "2022-12-31" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoField to sort by (e.g., title, value, stage_id)
limitNoNumber of items to return
startNoPagination start
org_idNoFilter by organization ID
statusNoFilter by deal status
sort_byNoSort direction
user_idNoFilter by user (owner) ID
stage_idNoFilter by stage ID
filter_idNoID of the filter to use
person_idNoFilter by person ID
pipeline_idNoFilter by pipeline ID
owned_by_youNoFilter deals owned by the authorized user (1 = yes, 0 = no)
add_time_fromNoFilter deals created on or after this date (YYYY-MM-DD). Applied client-side.
add_time_untilNoFilter deals created on or before this date (YYYY-MM-DD). Applied client-side.
Behavior4/5

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

No annotations provided, but description explains pagination behavior (default/max limit), client-side filtering caveat for date fields, and mentions alternative for complete results. Does not explicitly state read-only nature but is implied.

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?

Concise, well-structured with clear sections (workflow tips, common use cases). No redundant sentences; every sentence adds value.

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?

Comprehensive given 14 parameters and no output schema. Covers pagination, filtering, alternatives, and limitations. Missing explicit mention of return format but not required without output schema.

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?

All 14 parameters are described in schema (100% coverage). Description adds value by explaining enum meanings, providing usage patterns (e.g., owned_by_you=1), and examples for common scenarios.

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 lists deals with pagination and filtering. It distinguishes itself from sibling tools like deals_list_all_auto and deals_search, and includes common use cases.

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 guides when to use this tool versus alternatives (deals_list_all_auto for full pagination-free results). Warns about client-side filter limitations for date ranges and suggests alternative. Provides workflow tips and common 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/nubiia-dev/mcp-pipedrive'

If you have feedback or need assistance with the MCP directory API, please join our Discord server