Skip to main content
Glama
comma-compliance

pipedrive-mcp

by comma-compliance
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

pipedrive_organizations_list

Retrieve Pipedrive organizations using filters, pagination, sorting, and custom fields to power CRM searches, syncs, and reporting.

Instructions

List organizations with filters and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by organization IDs
limitNoNumber of items per page (default 25, max 100)
cursorNoOpaque token from previous response to fetch the next page
sort_byNoField to sort by
owner_idNoUser ID of the owner
filter_idNoPipedrive filter ID to apply
updated_sinceNoFilter by update time (ISO 8601 format, e.g. 2024-01-15T00:00:00Z)
updated_untilNoFilter by update time upper bound (ISO 8601 format)
include_fieldsNoAdditional fields to include in the response
sort_directionNoSort direction
custom_field_keysNoCustom field keys to include in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.1.1
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque token from previous response to fetch the next page"
    • addedInput schema / properties / custom_field_keys / description
      Added value: +"Custom field keys to include in the response"
    • addedInput schema / properties / filter_id / description
      Added value: +"Pipedrive filter ID to apply"
    • addedInput schema / properties / ids / description
      Added value: +"Filter by organization IDs"
    • addedInput schema / properties / include_fields / description
      Added value: +"Additional fields to include in the response"
    • addedInput schema / properties / include_fields / items / enum
      Added value: +[
+  "next_activity_id",
+  "last_activity_id",
+  "open_deals_count",
+  "related_open_deals_count",
+  "closed_deals_count",
+  "related_closed_deals_count",
+  "email_messages_count",
+  "people_count",
+  "activities_count",
+  "done_activities_count",
+  "undone_activities_count",
+  "files_count",
+  "notes_count",
+  "followers_count",
+  "won_deals_count",
+  "related_won_deals_count",
+  "lost_deals_count",
+  "related_lost_deals_count",
+  "smart_bcc_email"
+]
    • addedInput schema / properties / limit / description
      Added value: +"Number of items per page (default 25, max 100)"
    • addedInput schema / properties / owner_id / description
      Added value: +"User ID of the owner"
    • addedInput schema / properties / sort_by / description
      Added value: +"Field to sort by"
    • changedInput schema / properties / sort_by / enum
      Previous value: -[
-  "id",
-  "update_time",
-  "add_time",
-  "name"
-]New value: +[
+  "id",
+  "update_time",
+  "add_time"
+]
    • addedInput schema / properties / sort_direction / description
      Added value: +"Sort direction"
    • addedInput schema / properties / updated_since / description
      Added value: +"Filter by update time (ISO 8601 format, e.g. 2024-01-15T00:00:00Z)"
    • addedInput schema / properties / updated_until / description
      Added value: +"Filter by update time upper bound (ISO 8601 format)"
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does mention pagination, which is a useful behavioral hint, but omits read-only nature, authorization needs, rate limits, default page size, and cursor expiry behavior that an agent would need for reliable use.

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?

A single front-loaded sentence with no wasted words. However, it is arguably too terse given 11 parameters, and could have used one more sentence to route between list and search without becoming verbose.

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?

For an 11-parameter listing tool with no annotations and no output schema, the description is thin. It gives no behavioral context, no sibling routing, and no explanation of what the response contains, leaving the agent to rely entirely on the schema for a complex, filter-heavy operation.

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 description coverage is 100%, so the input schema already documents every parameter in detail. The description adds only the generic phrase 'with filters and pagination', which does not clarify any individual parameter beyond what the schema provides. Baseline 3 applies.

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?

States a clear verb ('List') and resource ('organizations') with a hint of scope ('filters and pagination'). However, it does not distinguish itself from close siblings like pipedrive_organizations_search or pipedrive_organizations_get, leaving the agent to infer the difference from the tool name alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as the search or get tools. The description merely restates that listing is possible, offering no routing information for an agent deciding among sibling list/search/get operations.

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