Skip to main content
Glama
ckalima

Pipedrive MCP Server

pipedrive_list_organizations

Read-onlyIdempotent

Retrieve organizations from Pipedrive CRM with filters by owner, name initial, or custom fields. Supports pagination and sorting for flexible data access.

Instructions

List organizations from Pipedrive with optional filtering by owner or first letter of name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoCursor for pagination
limitNoNumber of items (1-100)
filter_idNoFilter by saved filter ID
idsNoComma-separated organization IDs to fetch (max 100)
owner_idNoFilter by owner user ID
updated_sinceNoFilter organizations updated after this time (RFC3339 format)
updated_untilNoFilter organizations updated before this time (RFC3339 format)
sort_byNoField to sort by
sort_directionNoSort direction
include_fieldsNoInclude additional data in response
custom_fieldsNoInclude custom fields in response (comma-separated field keys or 'all')
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, etc. The description adds no behavioral context beyond listing, and includes a misleading filter mention, potentially confusing the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short, but critically incomplete and inaccurate. The single sentence omits essential context and includes a false claim, making it ineffective rather than concise.

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?

Given the lack of output schema and 11 parameters, the description fails to explain pagination, return format, or how to use filters effectively. Insufficient for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but the description claims a non-existent filter (first letter of name). It does not add meaningful semantics beyond the schema and introduces error.

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

Purpose3/5

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

The purpose is clear: list organizations with optional filtering. However, it inaccurately mentions filtering by 'first letter of name', which is not supported in the schema, reducing clarity.

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?

No guidance on when to use this tool over siblings like pipedrive_search_organizations or other list tools. The description does not specify context or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ckalima/pipedrive-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server