Skip to main content
Glama

pipelines_deals

List deals in a specific pipeline, filtering by stage, user, or custom filter. Supports pagination and pipeline summary.

Instructions

Get all deals in a specific pipeline.

Returns a list of deals in the pipeline with optional filtering by stage, user, or custom filter. Includes pagination support and optional summary statistics.

Workflow tips:

  • Filter by stage_id to see deals in specific stage

  • Use everyone=1 to see all deals (ignores filter_id and user_id)

  • Set get_summary=1 to include pipeline totals in additional_data

  • Use totals_convert_currency to convert values to specific currency

  • Supports pagination with start and limit parameters

  • Can apply custom filters with filter_id

Common use cases:

  • Get all deals in pipeline: { "id": 1 }

  • Get deals in specific stage: { "id": 1, "stage_id": 5 }

  • Get deals for user: { "id": 1, "user_id": 123 }

  • Get everyone's deals with summary: { "id": 1, "everyone": 1, "get_summary": 1 }

  • Paginated results: { "id": 1, "start": 0, "limit": 50 }

  • Convert to USD: { "id": 1, "totals_convert_currency": "USD", "get_summary": 1 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the pipeline
filter_idNoOnly return deals matching this filter
user_idNoOnly return deals owned by this user (defaults to authorized user)
everyoneNoSet to 1 to return deals owned by everyone (ignores filter_id and user_id)
stage_idNoOnly return deals in this specific stage
startNoPagination start offset (default: 0)
limitNoNumber of items per page
get_summaryNoSet to 1 to include pipeline summary in additional_data
totals_convert_currencyNo3-letter currency code (e.g., USD, EUR) or "default_currency"
Behavior4/5

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

No annotations provided, so description carries full burden. Clearly describes a read operation (returns list) with pagination, summary, and currency conversion behaviors. Does not mention permissions or rate limits, but the behavior is well-documented.

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 a clear main sentence followed by workflow tips and use cases. Slightly lengthy but all content adds value. Front-loaded with the core purpose.

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

Completeness5/5

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

Comprehensive coverage for a 9-parameter tool with no output schema. Includes examples for all common parameter combinations and explains dependencies. No gaps in parameter coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with all parameters described. The description adds significant value by explaining parameter interactions (e.g., everyone overwrites filter_id/user_id) and providing concrete examples for each parameter combination.

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 'Get all deals in a specific pipeline' with specific verb and resource. Distinguishes from sibling tools like deals_list and pipelines_get by specifying pipeline context and providing distinct 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 Guidelines4/5

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

Provides workflow tips and common use cases with example parameter combinations. Offers guidance on filtering, pagination, and summary usage. Could be more explicit about when not to use this tool versus alternatives like deals_search, but the examples cover many scenarios.

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