Skip to main content
Glama

pipedrive

by io.usefulapi

List persons

pipedrive_list_persons
Read-only

List persons (contacts), optionally filtered by filter/owner/org and sorted. Pipedrive REST: GET /api/v2/persons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (1–500, default 100).
cursorNoOpaque pagination cursor from a previous response's `next_cursor`.
org_idNoFilter by linked organization id.
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

A3.8/5.0
Behavior3/5

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

The annotation readOnlyHint=true already discloses the safe read-only nature. The description adds the REST GET path and clarifies persons as contacts, which slightly supplements but does not go beyond the annotation. No additional behavioral traits (e.g., pagination, rate limits) are disclosed.

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?

The description is two concise sentences: the first states the action and optional filters/sorting, the second provides the canonical REST endpoint. Every word earns its place and the most important information is 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 read-only list operation with 7 optional, fully documented parameters and no output schema, the description covers the essential purpose and API path. It omits explicit mention of pagination behavior, but the schema's cursor description compensates. The tool is simple enough that this is largely complete.

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%, with each parameter (limit, cursor, org_id, sort_by, owner_id, filter_id, sort_direction) having a clear description. The tool description merely lists parameter categories (filter/owner/org) without adding details beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ('List') and resource ('persons (contacts)'), clearly distinguishing it from get/single-entity tools like pipedrive_get_person and from search tools like pipedrive_search_persons. Mentioning optional filters and sorting adds scope without ambiguity.

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 use cases via 'optionally filtered by filter/owner/org and sorted' but does not explicitly state when to prefer this over siblings like pipedrive_search_persons or pipedrive_get_person. No exclusions or alternative tool recommendations are provided.

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