Search Pipedrive deals by title or keyword to locate matching records quickly. Provide a term and optional result limit to retrieve the deals you need.
Search Pipedrive deals by term.
| Name | Required | Description | Default |
|---|---|---|---|
| term | Yes | Search term (deal title or keyword) | |
| limit | No | Results to return (max 100, default 25) | |
| api_token | Yes | Pipedrive API token |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare that this is a read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds no behavioral context such as pagination, result limits, or authentication requirements, but it does not contradict the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. Every word contributes to stating the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple search tool with full schema coverage and rich annotations, the description is minimally sufficient. However, it does not mention result behavior such as default/max limits or pagination, and there is no output schema to cover return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents term, limit, and api_token. The description only echoes that search is by term and does not add meaning beyond the parameter descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: search Pipedrive deals by term. It is clear what the tool does, but it does not name the sibling pipedrive_list_deals or otherwise explain how this differs from listing all deals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool instead of pipedrive_list_deals or other alternatives. The phrase 'by term' implies a search use case, but the description gives no when-to-use or when-not-to-use criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.