Skip to main content
Glama
comma-compliance

pipedrive-mcp

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

pipedrive_persons_get

Fetch a Pipedrive person by ID to view full details, resolved custom fields, and optional activity, deal, or marketing data.

Instructions

Get a single person by ID with full details including resolved custom fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idYesThe person ID to retrieve
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
custom_field_keysNoCustom field keys to include in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • addedInput schema / properties / custom_field_keys / description
      Added value: +"Custom field keys to include in the response"
    • 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"
+]
  2. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden, and it discloses the notable return behavior ('full details including resolved custom fields') which is useful. However it says nothing about read-only nature, permission requirements, or behavior when the ID does not exist. Acceptable for a simple single-record getter, but not rich.

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?

One sentence, front-loaded with the core verb and resource, with the return-shape qualifier appended. No wasted words.

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?

With no output schema, the description does summarize the return ('full details including resolved custom fields'), which is the main thing an agent needs to judge usefulness. Error behavior on a missing ID and any permission constraints remain unstated, but the tool is a simple getter, so the gap is minor.

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 three parameters (person_id, include_fields, custom_field_keys) are already documented in the schema, including the marketing-app constraint on marketing_status/doi_status. The description's mention of 'resolved custom fields' loosely maps to custom_field_keys but adds no syntax or format detail beyond the schema.

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 with scoping: 'Get a single person by ID'. This clearly distinguishes it from pipedrive_persons_list and pipedrive_persons_search, which return many records. It stops short of naming those siblings explicitly, so it is clear but not fully differentiated.

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?

The phrase 'by ID' implies usage after an ID is known, and the sibling set makes search/list alternatives inferable, but the description never states when to use this versus persons_search or persons_list. Guidance is implied rather than explicit.

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