Skip to main content
Glama
comma-compliance

pipedrive-mcp

by comma-compliance
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

pipedrive_deals_list

List Pipedrive deals with filters for stage, status, owner, and dates, plus pagination. Returns compact summaries with IDs, titles, stages, values, and linked entity IDs.

Instructions

List deals with filters and pagination. Returns compact deal summaries with IDs, titles, stages, values, and linked entity IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by deal IDs
limitNoNumber of items per page (default 25, max 100)
cursorNoOpaque token from previous response to fetch the next page
org_idNoFilter by linked organization ID
statusNoFilter by deal status
sort_byNoField to sort by
owner_idNoUser ID of the owner
stage_idNoFilter by stage ID
filter_idNoPipedrive filter ID to apply
person_idNoFilter by linked person ID
pipeline_idNoFilter by pipeline ID
updated_sinceNoFilter by update time (ISO 8601 format, e.g. 2024-01-15T00:00:00Z)
updated_untilNoFilter by update time upper bound (ISO 8601 format)
include_fieldsNoAdditional fields to include in the response
sort_directionNoSort direction
custom_field_keysNoCustom field keys to include in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv1.1.1
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque token from previous response to fetch the next page"
    • addedInput schema / properties / custom_field_keys / description
      Added value: +"Custom field keys to include in the response"
    • addedInput schema / properties / filter_id / description
      Added value: +"Pipedrive filter ID to apply"
    • addedInput schema / properties / ids / description
      Added value: +"Filter by deal IDs"
    • addedInput schema / properties / include_fields / description
      Added value: +"Additional fields to include in the response"
    • addedInput schema / properties / include_fields / items / enum
      Added value: +[
+  "next_activity_id",
+  "last_activity_id",
+  "first_won_time",
+  "products_count",
+  "files_count",
+  "notes_count",
+  "followers_count",
+  "email_messages_count",
+  "activities_count",
+  "done_activities_count",
+  "undone_activities_count",
+  "participants_count",
+  "last_incoming_mail_time",
+  "last_outgoing_mail_time",
+  "smart_bcc_email",
+  "source_lead_id"
+]
    • addedInput schema / properties / limit / description
      Added value: +"Number of items per page (default 25, max 100)"
    • addedInput schema / properties / org_id / description
      Added value: +"Filter by linked organization ID"
    • addedInput schema / properties / owner_id / description
      Added value: +"User ID of the owner"
    • addedInput schema / properties / person_id / description
      Added value: +"Filter by linked person ID"
    • addedInput schema / properties / pipeline_id / description
      Added value: +"Filter by pipeline ID"
    • addedInput schema / properties / sort_by / description
      Added value: +"Field to sort by"
    • changedInput schema / properties / sort_by / enum
      Previous value: -[
-  "id",
-  "update_time",
-  "add_time",
-  "title",
-  "value"
-]New value: +[
+  "id",
+  "update_time",
+  "add_time"
+]
    • addedInput schema / properties / sort_direction / description
      Added value: +"Sort direction"
    • addedInput schema / properties / stage_id / description
      Added value: +"Filter by stage ID"
    • addedInput schema / properties / status / description
      Added value: +"Filter by deal status"
    • addedInput schema / properties / updated_since / description
      Added value: +"Filter by update time (ISO 8601 format, e.g. 2024-01-15T00:00:00Z)"
    • addedInput schema / properties / updated_until / description
      Added value: +"Filter by update time upper bound (ISO 8601 format)"
  2. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return shape (compact summaries with IDs, titles, stages, values, linked entity IDs) and implies pagination, but says nothing about authorization scope, rate limits, or whether filtering is server-side. For a 16-parameter read tool with zero annotation coverage this is thin.

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?

Two sentences, no filler, and it front-loads the core action and the return contract. Every clause earns its place.

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?

With 16 optional parameters, no output schema, and no annotations, the description covers the basics (listing, filtering, pagination, return fields) but leaves the agent without routing guidance versus sibling list/search/summary tools and without any filter-combination or empty-result 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 description coverage is 100%, so all 16 parameters are already documented in the schema. The description adds no filter-specific semantics or interaction rules (e.g. how ids combines with status, or how filter_id interacts with other filters), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List deals') plus the two operational dimensions (filters, pagination) and the return shape. It is clear and not tautological, but it never distinguishes itself from close siblings like pipedrive_deals_search, pipedrive_deals_summary, or pipedrive_my_open_deals.

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

Usage Guidelines2/5

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

No when-to-use guidance at all. With sibling tools such as pipedrive_deals_search, pipedrive_my_open_deals, and pipedrive_stale_deals in the same family, the description gives the agent no condition for choosing this tool over those.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools