Pipedrive MCP Server

get_organizations_summary

Retrieve a summarized list of organizations from Pipedrive CRM with essential fields only, optimized for efficient data access and token usage.

Instructions

Get a summarized list of organizations (optimized for token usage) - shows essential fields only

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_organizations_summary"
  }
}

Input Schema

Name	Required	Description
`start`	No	Pagination start (default: 0)
`limit`	No	Number of items to return (default: 20, max: 50 for summary)
`user_id`	No	Filter by user ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, description adds valuable behavioral context about token optimization and field reduction. However, omits other behavioral traits like confirming read-only safety, pagination behavior, or cache characteristics that annotations would typically cover.

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?

Single efficient sentence with clear front-loading. Parenthetical '(optimized for token usage)' and dash 'shows essential fields only' both earn their place by clarifying the summary nature without verbosity.

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?

Adequate for a 3-parameter read tool: explains the summary nature compensating for lack of output schema. However, with no annotations and no output schema, could benefit from mentioning pagination behavior or filtering capabilities (user_id) explicitly in the description.

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 has 100% description coverage (start, limit, user_id). Description provides baseline context by implying pagination via 'list', but doesn't add parameter-specific semantics, syntax, or format details beyond what the schema already provides.

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?

Clear verb 'Get' + resource 'organizations' with specific modifier 'summarized'. Distinguishes from sibling 'get_organizations' via 'essential fields only' and 'optimized for token usage', though it doesn't explicitly name the alternative tool.

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?

Provides implied usage guidance through 'optimized for token usage', suggesting when to use (token-constrained contexts). However, lacks explicit 'when-not-to-use' or direct comparison to 'get_organizations' or 'search_organizations' siblings.

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