Skip to main content
Glama
Sign In
Pipedrive MCP Server

Pipedrive MCP Server

by ckalima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pipedrive_list_deal_installments

Read-onlyIdempotent

List payment installments for specified deal IDs, with options for pagination and sorting. Retrieve installment details from Pipedrive.

Instructions

List installments across one or more deals. Requires deal_ids. Growth+ plan required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deal_ids": "<deal_ids>"
    },
    "name": "pipedrive_list_deal_installments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items (1-100)
cursorNoCursor for pagination
sort_byNoField to sort by
deal_idsYesDeal IDs to fetch installments for (1-100, required)
sort_directionNoSort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, making the safety profile clear. The description adds the plan requirement but no additional behavioral details like pagination or return format.

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 with no wasted words, each providing distinct information: what the tool does and its prerequisites.

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 a list tool with good annotations and full schema coverage, the description is sufficient but could be more complete by mentioning pagination or typical use cases.

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?

All parameters are fully described in the schema (100% coverage), so the description adds no extra meaning beyond stating that deal_ids is required, which is already in the schema.

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

Purpose5/5

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

The description clearly states the tool lists installments across one or more deals, with a specific verb ('List') and resource ('installments'). It distinguishes from sibling tools like add/update installment tools by being a read operation.

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 description provides prerequisites (deal_ids required, Growth+ plan required) but does not give when-to-use or when-not-to-use guidance relative to alternatives such as pipedrive_list_deal_discounts.

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