Skip to main content
Glama
Sign In
Pipedrive MCP Server

Pipedrive MCP Server

by WillDent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search-persons

Read-onlyIdempotent

Search for persons in Pipedrive by name or other criteria. Retrieve matching records with optional pagination and result limits.

Instructions

Search Pipedrive persons.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "<term>"
    },
    "name": "search-persons"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already cover safety (read-only, non-destructive, idempotent, open-world). The description adds no behavioral context beyond those annotations, such as pagination behavior or query limitations.

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?

At two words, the description is too short to be informative. It lacks structure and does not earn its place; essential information is missing.

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?

Despite rich annotations, the description omits key details such as required parameter semantics (term), pagination (cursor), and output format. The tool is inadequately documented for an agent to use effectively.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any parameter (term, limit, cursor). The agent must infer meaning from parameter names alone, which is insufficient for correct invocation.

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?

Description states 'Search Pipedrive persons.' It clearly identifies the action (search) and resource (persons). This distinguishes it from sibling tools like 'get-person' (single fetch) and 'get-persons' (likely list all), but provides no additional detail about the type of search.

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 is provided on when to use this tool versus alternatives such as 'get-persons' or 'search-deals'. The agent receives no help in deciding which search to invoke.

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