Skip to main content
Glama
ckalima

Pipedrive MCP Server

pipedrive_list_deals

Read-onlyIdempotent

List deals from Pipedrive with filtering by owner, person, organization, pipeline, stage, or status. Returns paginated results.

Instructions

List deals from Pipedrive with optional filtering by owner, person, organization, pipeline, stage, or status. Returns paginated results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoCursor for pagination (from previous response)
limitNoNumber of items to return (1-100, default 50)
filter_idNoFilter by saved filter ID
idsNoComma-separated deal IDs to fetch (max 100)
owner_idNoFilter by owner user ID
person_idNoFilter by linked person ID
org_idNoFilter by linked organization ID
pipeline_idNoFilter by pipeline ID
stage_idNoFilter by stage ID
statusNoFilter by deal status (omit to return all non-deleted deals)
updated_sinceNoFilter deals updated after this time (RFC3339 format, e.g. 2024-01-01T00:00:00Z)
updated_untilNoFilter deals updated before this time (RFC3339 format)
sort_byNoField to sort by
sort_directionNoSort direction (default: desc)
include_fieldsNoComma-separated extra fields (v2 enum, e.g. next_activity_id, last_activity_id, products_count, files_count, notes_count, followers_count)
custom_fieldsNoInclude custom fields in response (comma-separated field keys or 'all')
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. Description adds that results are paginated, which is a useful behavioral note beyond annotations. No contradictions.

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?

Single sentence that front-loads the purpose and key capabilities, with no unnecessary words. Every element earns its place.

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 16 parameters, no output schema, and rich annotations, the description covers essential filtering and pagination. It could briefly mention pagination details (cursor/limit) but the schema handles that, so completeness is adequate.

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 descriptions for all 16 parameters. The description only highlights a subset of filter options and does not add additional meaning or context beyond the schema's own field descriptions.

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 'List deals from Pipedrive' with specific verb and resource, and lists common filtering options, distinguishing it from sibling list tools like list_archived_deals or list_deal_followers.

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

Usage Guidelines3/5

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

Mentions optional filtering but does not explicitly advise when to use this tool over alternatives like pipedrive_search_deals for text search or list_archived_deals for deleted deals. No 'when not to use' guidance provided.

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/ckalima/pipedrive-mcp-server'

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