Skip to main content
Glama

pipedrive

by io.usefulapi

List organizations

pipedrive_list_organizations
Read-only

List organizations, optionally filtered by filter/owner and sorted. Pipedrive REST: GET /api/v2/organizations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (1–500, default 100).
cursorNoOpaque pagination cursor from a previous response's `next_cursor`.
sort_byNoField to sort by — 'id', 'update_time' or 'add_time'.
owner_idNoFilter by owner (user) id.
filter_idNoFilter by a saved filter id.
sort_directionNoSort direction — 'asc' or 'desc'.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description adds the REST GET endpoint and optional filter/sort behavior, which is consistent. No contradiction, but no additional behavioral context like pagination or return format beyond what the schema provides.

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?

Two sentences with no wasted words. The first sentence states the core behavior, and the second provides the REST endpoint reference. Well structured and front-loaded.

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

Completeness4/5

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

For a simple list operation with full schema coverage and a readOnly annotation, the description is adequate. It lacks explicit alternative tool guidance and return format details, but these are not critical given the provided schema and annotations.

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 parameters are fully documented. The description references 'filter/owner' and 'sorted', corresponding to filter_id, owner_id, sort_by, and sort_direction, but adds no new syntax or details beyond the schema.

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 states 'List organizations' with optional filtering and sorting, using a specific verb and resource. It distinguishes itself from sibling tools like get_organization and search_organizations by focusing on the list operation with filter/sort capabilities.

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

Usage Guidelines4/5

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

The description gives clear context: listing organizations with optional filters by filter/owner and sorting. It does not explicitly name alternatives or when-not-to-use, but the context is clear enough in the presence of sibling tools.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear separation between create, get, list, and search operations. The global search tool is explicitly differentiated from entity-specific searches, and pipelines/stages/current_user are unique. No two tools appear to serve the same purpose.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern (e.g., list_deals, get_person, create_activity), with the exception of 'add_note' using 'add' instead of 'create'. This is a minor deviation that does not cause confusion, but the inconsistency between add and create is noticeable.

Tool Count4/5

At 19 tools, the server covers a broad set of CRM entities and operations, which is reasonable for the scope. While it is on the heavier side, each tool serves a distinct function and none are redundant. The count feels justified for a comprehensive CRM integration.

Completeness2/5

The server lacks update and delete operations for all entities, and there is no create operation for organizations, pipelines, or stages. This creates significant gaps that would prevent agents from modifying existing records or creating certain entities. The read and search capabilities are solid, but the lifecycle coverage is severely incomplete.

Resources