Skip to main content
Glama

deals_search

Search deals by title, notes, or custom fields using a text query. Filter by status, person, or organization for precise results.

Instructions

Search for deals using a text query.

Searches deals by title, notes, or custom fields. Much faster than filtering all deals.

Workflow tips:

  • Search is case-insensitive by default

  • Minimum 2 characters for search term

  • Use exact_match=true for precise matching

  • Combine with person_id or org_id to narrow results

  • Use status filter to search only open/won/lost deals

  • Results are cached for 5 minutes

Common use cases:

  • Search by title: { "term": "acme" }

  • Exact match: { "term": "ACME Corp Deal", "exact_match": true }

  • Search for person's deals: { "term": "software", "person_id": 123 }

  • Search open deals only: { "term": "contract", "status": "open" }

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term (minimum 2 characters)
fieldsNoFields to search in (default: all)
exact_matchNoWhether to perform exact match search
person_idNoFilter by person ID
org_idNoFilter by organization ID
statusNoFilter by deal status
include_fieldsNoComma-separated list of fields to include in response
startNoPagination start
limitNoNumber of items to return (max 500)
Behavior4/5

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

Discloses case-insensitivity, minimum 2 characters, exact_match option, caching for 5 minutes, and pagination. No annotations exist, so description carries full burden and does it well, though error handling is omitted.

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?

Intro + bullet points for workflow tips and use cases. No fluff, every sentence adds value. Well-organized 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 all major aspects for search tool: parameters, examples, performance, caching. Lacks output schema/return format, but pagination and field filtering are addressed. Sufficient for agent invocation.

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?

Input schema has 100% coverage, but description adds examples and defaults (e.g., fields default 'all', status filter values). Explains behavior like caching and case-insensitivity beyond schema.

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?

Description clearly states 'Search for deals using a text query' and specifies searched fields (title, notes, custom fields). Distinguishes from sibling tools by noting it is 'Much faster than filtering all deals.'

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, common use cases, and parameters for filtering. Explicitly mentions performance advantage over listing all deals, but does not list alternatives or when not to use.

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