Skip to main content
Glama
Sign In

Pipedrive

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Pipedrive List Deals

pipedrive_list_deals
Read-onlyIdempotent

View all deals in your pipeline. Returns deal IDs, titles, values, stages, and owners. Use pipedrive_get_deal for full details on a specific deal.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-pipedrive-api-key"
    },
    "name": "pipedrive_list_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (max 500, default 50)
startNoPagination start (default 0)
statusNoFilter by status: open, won, lost, deleted, all_not_deleted (default: all_not_deleted)
_apiKeyYesPipedrive API token

Output Schema

NameRequiredDescriptionDefault
dataNoList of deals
successNoWhether the request succeeded
additional_dataNoPagination and metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "additional_data": {
+      "description": "Pagination and metadata",
+      "type": "object"
+    },
+    "data": {
+      "description": "List of deals",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Deal ID",
+            "type": "number"
+          },
+          "owner_id": {
+            "description": "Deal owner ID",
+            "type": "number"
+          },
+          "stage_id": {
+            "description": "Pipeline stage ID",
+            "type": "number"
+          },
+          "status": {
+            "description": "Deal status",
+            "type": "string"
+          },
+          "title": {
+            "description": "Deal title",
+            "type": "string"
+          },
+          "value": {
+            "description": "Deal value",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "description": "Whether the request succeeded",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-pipedrive-api-key"
+  },
+  {
+    "_apiKey": "your-pipedrive-api-key",
+    "limit": 100,
+    "status": "won"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful context beyond annotations by specifying the returned fields (deal IDs, titles, values, stages, owners), which helps the agent understand the output. No contradictions.

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?

The description is two sentences: front-loaded with the action and resource, then a summary of returned data, then an explicit pointer to a sibling tool. Every sentence earns its place with no filler.

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

Completeness5/5

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

Given the tool's low complexity, full schema coverage, rich annotations, and an output schema, the description provides sufficient context. It communicates the tool's purpose, key return fields, and directs to the appropriate alternative for deeper detail.

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?

The input schema already covers 100% of the parameter descriptions (limit, start, status, _apiKey), so the description does not need to explain them. It adds no additional parameter-specific semantics beyond what the schema provides.

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 uses a specific verb 'View all deals' and identifies the resource 'your pipeline.' It clearly distinguishes from siblings like pipedrive_get_deal and pipedrive_list_persons by stating it returns deal IDs, titles, values, stages, and owners, and it explicitly points to pipedrive_get_deal for full details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly guides the agent to use pipedrive_get_deal for full details on a specific deal, which provides a clear alternative and implies when not to use this list tool. This satisfies the need for when/when-not/alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pipedrive toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources