Skip to main content
Glama

search_deals

Search and filter deals by title, person, organization, and status to quickly find specific deals.

Instructions

Search for deals with advanced filtering options.

Performs a deal-specific search with additional filtering by person, organization, and status.

Workflow tips:

  • Search term must be at least 2 characters

  • Filter by person_id, org_id to narrow results

  • Filter by status: open, won, lost, all_not_deleted

  • Specify fields to search: title, notes, custom fields

  • Use include_fields to limit response data

  • Results ordered by relevance

Common use cases:

  • Search deals by title: { "term": "contract" }

  • Search open deals: { "term": "acme", "status": "open" }

  • Search deals for person: { "term": "proposal", "person_id": 123 }

  • Search specific fields: { "term": "urgent", "fields": "title,notes" }

  • Limit response data: { "term": "deal", "include_fields": "title,value,stage_id" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term (min 2 chars)
fieldsNoComma-separated field names to search
exact_matchNoPerform exact match search
person_idNoFilter by associated person ID
org_idNoFilter by associated organization ID
statusNoFilter by deal status
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?

With no annotations provided, the description carries the full burden. It implies read-only behavior through search semantics and mentions result ordering, but does not explicitly state that it's non-destructive, nor does it disclose rate limits or auth requirements. Additional behavioral context would be beneficial.

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 concise and well-structured: a summary, bullet-point workflow tips, and common use cases. Every sentence adds value without redundancy. It is front-loaded with the 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?

For a 9-parameter tool without output schema, the description covers the main functionality and most parameters through examples. However, pagination parameters (start, limit) are not mentioned in the tips or examples, leaving a minor gap for agents needing to handle pagination.

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 coverage is 100%, so parameters are documented. The description adds common use cases that illustrate parameter combinations, but does not provide deeper semantic meaning beyond what the schema already conveys. It matches the baseline expectation.

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 tool searches for deals with advanced filtering, and provides specific filtering options (person, org, status) that distinguish it from basic search tools like deals_search.

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?

Workflow tips provide clear usage guidance including search term length, filter fields, and status options. Common use cases give practical examples. However, it does not explicitly specify when to use this tool over alternatives like deals_search.

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