Skip to main content
Glama
comma-compliance

pipedrive-mcp

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

pipedrive_persons_list

List CRM persons with filters and pagination to find contacts by organization, owner, update time, or custom fields.

Instructions

List persons with filters and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by person IDs
limitNoNumber of items per page (default 25, max 100)
cursorNoOpaque token from previous response to fetch the next page
org_idNoFilter by organization ID
sort_byNoField to sort by
owner_idNoUser ID of the owner
filter_idNoPipedrive filter ID to apply
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. marketing_status and doi_status can only be included if the company has the marketing app enabled
sort_directionNoSort direction
custom_field_keysNoCustom field keys to include in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 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 person IDs"
    • addedInput schema / properties / include_fields / description
      Added value: +"Additional fields to include in the response. marketing_status and doi_status can only be included if the company has the marketing app enabled"
    • addedInput schema / properties / include_fields / items / enum
      Added value: +[
+  "next_activity_id",
+  "last_activity_id",
+  "open_deals_count",
+  "related_open_deals_count",
+  "closed_deals_count",
+  "related_closed_deals_count",
+  "participant_open_deals_count",
+  "participant_closed_deals_count",
+  "email_messages_count",
+  "activities_count",
+  "done_activities_count",
+  "undone_activities_count",
+  "files_count",
+  "notes_count",
+  "followers_count",
+  "won_deals_count",
+  "related_won_deals_count",
+  "lost_deals_count",
+  "related_lost_deals_count",
+  "last_incoming_mail_time",
+  "last_outgoing_mail_time",
+  "marketing_status",
+  "doi_status",
+  "smart_bcc_email"
+]
    • 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 organization ID"
    • addedInput schema / properties / owner_id / description
      Added value: +"User ID of the owner"
    • 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",
-  "name"
-]New value: +[
+  "id",
+  "update_time",
+  "add_time"
+]
    • addedInput schema / properties / sort_direction / description
      Added value: +"Sort direction"
    • 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

C2.9/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, yet it discloses almost nothing: no auth/permission requirements, no rate limits, no return shape, and only the bare word 'pagination' without cursor semantics. A read-only list is relatively safe, but the transparency gap is real.

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?

A single short sentence, front-loaded with the verb and resource. It is efficient, though borderline under-specified rather than genuinely concise given the tool's 12 parameters.

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

Completeness2/5

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

For a 12-parameter list tool with no annotations and no output schema, the description is far too thin. It omits pagination mechanics, default/max results behavior, and any differentiation from the search sibling, leaving the agent to infer usage entirely from the schema.

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 12 parameters are already documented in the schema, including enums and the marketing-app caveat. The description adds no parameter meaning beyond that, which is the expected baseline 3.

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 (List) and resource (persons) with scope modifiers for filters and pagination, so the agent knows exactly what the tool does. However, it does not distinguish itself from the closely named sibling pipedrive_persons_search, which an agent may confuse it with.

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?

The description gives no when-to-use guidance and no exclusions. With pipedrive_persons_search, pipedrive_persons_get, and pipedrive_persons_list all present, the agent gets no signal on which to choose; the mention of 'filters' is a weak implied hint at best.

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