Pipedrive MCP Server

pipedrive_get_organization

Read-onlyIdempotent

Fetch detailed organization information by ID, including custom fields, for CRM data retrieval and management.

Instructions

Get detailed information about a specific organization by ID.

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": {
      "id": "<id>"
    },
    "name": "pipedrive_get_organization"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The organization ID
`custom_fields`	No	Include custom fields in response (comma-separated field keys or 'all')
`include_fields`	No	Include additional data in response

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 30, 2026

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. The description 'Get detailed information' is consistent but adds no additional behavioral context beyond what annotations provide.

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?

Single sentence that is efficient and front-loaded. No unnecessary words or redundant details.

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?

While the description is minimal, it covers the core purpose. However, for a 'get by ID' tool with no output schema, it could clarify what 'detailed information' includes (e.g., full organization object with all fields).

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 coverage is 100% so the schema already documents all parameters. The description does not add new meaning beyond the schema; it only reiterates the resource type.

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 specifies the action ('Get detailed information') and the resource ('specific organization by ID'). It distinguishes from sibling list/search tools that return multiple records.

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 implies usage when you have a specific organization ID, but does not explicitly state when to use this tool vs alternatives like list or search tools. No when-not-to-use guidance is provided.

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

Deploy Server