Skip to main content
Glama
comma-compliance

pipedrive-mcp

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

pipedrive_leads_list

Retrieve Pipedrive leads using filters like owner, person, organization, or archived status, and paginate results with a cursor.

Instructions

List leads with filters and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field and direction (e.g. 'add_time ASC')
limitNoNumber of items per page (default 25, max 100)
cursorNoOpaque token from previous response to fetch the next page
owner_idNoUser ID of the owner
filter_idNoPipedrive filter ID to apply
person_idNoFilter by person ID
archived_statusNoFilter by archived status
organization_idNoFilter by organization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.1.1
    • addedInput schema / properties / archived_status / description
      Added value: +"Filter by archived status"
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque token from previous response to fetch the next page"
    • addedInput schema / properties / filter_id / description
      Added value: +"Pipedrive filter ID to apply"
    • addedInput schema / properties / limit / description
      Added value: +"Number of items per page (default 25, max 100)"
    • addedInput schema / properties / organization_id / description
      Added value: +"Filter by 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 person ID"
    • addedInput schema / properties / sort / description
      Added value: +"Sort field and direction (e.g. 'add_time ASC')"
  2. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It implies a read-only listing operation and discloses pagination support, but omits auth needs, rate limits, whether all leads are returned, and return format details.

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?

The description is a single front-loaded sentence with no wasted words. It is very terse, but under-specification is penalized in other dimensions; structurally it is appropriately concise.

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?

For an 8-parameter list tool with many siblings and no output schema, the description is minimally adequate because the schema fully documents the filtering and pagination options. However, it does not help the agent choose between list/search/get or understand return behavior, leaving clear gaps.

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 8 parameters are already documented in the input schema. The description only mentions filters and pagination generically and adds no syntax, defaults, or semantics 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?

The description states a clear verb ('List') and resource ('leads'), plus scope ('with filters and pagination'). It does not differentiate this from sibling tools like pipedrive_leads_search or pipedrive_leads_get, but the core purpose is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives such as pipedrive_leads_search, pipedrive_leads_get, or other list tools. No prerequisites or exclusions are provided, leaving selection entirely to inference.

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