Skip to main content
Glama

search_persons

Search for persons by name, email, or phone with filters for organization and exact match. Specify search fields and limit response data for efficient retrieval.

Instructions

Search for persons with advanced filtering options.

Performs a person-specific search with additional filtering by organization.

Workflow tips:

  • Search term must be at least 2 characters

  • Filter by org_id to find persons in specific organizations

  • Specify fields to search: name, email, phone, custom fields

  • Use include_fields to limit response data

  • Use exact_match for precise searches

  • Results ordered by relevance

Common use cases:

  • Search by name: { "term": "john smith" }

  • Search by email: { "term": "john@example.com", "fields": "email" }

  • Search in organization: { "term": "smith", "org_id": 123 }

  • Search phone numbers: { "term": "+1234567890", "fields": "phone" }

  • Limit response: { "term": "john", "include_fields": "name,email,phone" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term (min 2 chars)
fieldsNoComma-separated field names to search
exact_matchNoPerform exact match search
org_idNoFilter by associated organization ID
include_fieldsNoComma-separated fields to include in response
startNoPagination start
limitNoNumber of items to return
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions result ordering by relevance, min term length, and default pagination values. Lacks details on authentication, rate limits, or error behavior. Adequate but not exhaustive.

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?

Well-structured with main description, bulleted workflow tips, and code examples. Slight redundancy in opening phrases, but overall front-loaded and easy to scan.

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?

Covers essential usage aspects: search term constraints, filtering options, field selection, pagination defaults, and examples. No output schema, but description doesn't need to explain return values. Lacks pagination limits or error handling, but sufficient for typical search use.

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?

All 7 parameters are described in schema, but description adds value with concrete usage examples (e.g., email search, org filter, field selection) that illustrate parameter combinations beyond schema definitions.

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?

Clearly states 'Search for persons' with advanced filtering. Distinguishes from sibling search tools (e.g., deals, organizations) by specifying it's person-specific and includes org_id filtering.

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?

Provides workflow tips such as minimum 2-character term, field-specific search, org_id filter, exact_match, and include_fields. Includes common use case examples. However, it does not explicitly state when not to use or compare to alternatives.

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