Skip to main content
Glama

persons_search

Search for persons in Pipedrive by name, email, phone, or notes with fuzzy or exact matching. Filter results by organization or specific fields.

Instructions

Search for persons by name, email, phone, or notes.

The search uses Pipedrive's intelligent search that:

  • Searches across multiple fields (name, email, phone, notes, custom fields)

  • Supports fuzzy matching by default

  • Returns ranked results

Search options:

  • term: Search term (minimum 2 characters)

  • fields: Specific fields to search in (default: all fields)

  • exact_match: Use exact matching instead of fuzzy search

  • org_id: Filter results by organization

  • include_fields: Additional fields to include in response

The search is case-insensitive and supports partial matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term (minimum 2 characters)
fieldsNoFields to search in: name, email, phone, notes, custom_fields, or all (default: all)
exact_matchNoUse exact match instead of fuzzy search (default: false)
org_idNoFilter by organization ID
include_fieldsNoComma-separated list of additional fields to include
startNoPagination start (default: 0)
limitNoNumber of results to return, max 500 (default: 100)
Behavior4/5

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

No annotations are provided, so the description must supply behavioral traits. It does so by detailing intelligent search, fuzzy matching, case-insensitivity, partial matches, ranked results, and a minimum 2-character requirement. It does not describe pagination behavior, but that is covered in the schema. No contradictions.

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?

The description is well-structured with bullet points and clear sections. However, it is somewhat lengthy and could be more concise without losing meaning. It is front-loaded with the core purpose.

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?

Given 7 parameters, no output schema, and no annotations, the description covers the core search behavior thoroughly. It explains what the search does, the options, and the intelligent matching. Pagination is covered in the schema. It would benefit from mentioning the response format, but overall complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds significant meaning beyond the schema: it explains the search options (fuzzy vs exact, field filtering, case-insensitivity) and the behavior of the search engine. This goes beyond mere parameter descriptions.

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 the verb 'Search', the resource 'persons', and the scope (by name, email, phone, or notes). It distinguishes from siblings like search_universal and search_organizations by being person-specific. The detailed explanation of intelligent search features reinforces its purpose.

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 provides context on when to use the tool (searching persons with various options) and explains search behavior (fuzzy matching, case-insensitive). However, it does not differentiate from the sibling tool 'search_persons', which appears to be an alternative endpoint. This lack of explicit guidance on when to use which reduces clarity.

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/iamsamuelfraga/mcp-pipedrive'

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