Skip to main content
Glama
comma-compliance

pipedrive-mcp

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

pipedrive_products_list

Retrieve products from Pipedrive using filters, sorting, and cursor pagination to find or page through catalog items.

Instructions

List products with filters and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by product IDs
limitNoNumber of items per page (default 25, max 100)
cursorNoOpaque token from previous response to fetch the next page
sort_byNo
owner_idNoUser ID of the owner
filter_idNoPipedrive filter ID to apply
sort_directionNoSort direction
custom_field_keysNoCustom field keys to include in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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 product IDs"
    • addedInput schema / properties / limit / description
      Added value: +"Number of items per page (default 25, max 100)"
    • addedInput schema / properties / owner_id / description
      Added value: +"User ID of the owner"
    • addedInput schema / properties / sort_direction / description
      Added value: +"Sort direction"
  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-disclosure burden. It mentions filters and pagination at a high level, but does not state that the operation is read-only, describe auth or permission requirements, or explain pagination behavior beyond what the schema already provides.

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 front-loaded sentence with no filler, so it is concise and easy to scan. It is perhaps too sparse for the tool's complexity, but it avoids repetition or verbosity.

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 an 8-parameter list tool with no annotations and no output schema, the description is under-specified. It should at least distinguish this from product search/get siblings and clarify expected read-only list behavior with filters and pagination.

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 88%, so the schema already documents nearly all parameters in detail. The description adds only the general terms 'filters' and 'pagination' and does not add parameter-level meaning beyond that.

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 ('products'), so the basic purpose is clear. However, it does not distinguish this tool from close siblings such as pipedrive_products_search or pipedrive_products_get, so an agent must infer the difference from the name alone.

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 explicit guidance on when to use this tool versus alternatives. It implies listing with filters and pagination, but with many sibling list/search/get tools, there is no routing context for selecting this one.

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