Pipedrive MCP Server

search_summarized

Search Pipedrive CRM items with summarized results to quickly find deals, contacts, organizations, or products using optimized token usage.

Instructions

Search across all Pipedrive items with summarized results (token-optimized)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "<term>"
    },
    "name": "search_summarized"
  }
}

Input Schema

Name	Required	Description
`term`	Yes	Search term
`item_types`	No	Comma-separated list of item types to search (deal,person,organization,product)
`limit`	No	Number of results to return (default: 10, max: 20 for summary)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 1, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the burden and discloses key behavioral traits: 'summarized results' and 'token-optimized' indicate reduced payload size versus full searches. However, it omits details about what specific fields are returned, omitted, or how the summary is constructed.

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?

Extremely concise at 9 words. Every element earns its place: action ('Search'), scope ('across all Pipedrive items'), output type ('summarized results'), and key characteristic ('token-optimized'). No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Input parameters are fully schema-documented, but given zero annotations, no output schema, and the presence of multiple overlapping search siblings, the description should explain what 'summarized' actually includes/excludes to aid tool selection. Adequate but incomplete.

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%, establishing a baseline of 3. The description adds no specific parameter guidance beyond what's in the schema (e.g., no format details for 'item_types' comma-separation or 'term' syntax beyond the schema's 'Search term').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'Search' and resource 'Pipedrive items'. The phrase 'summarized results (token-optimized)' distinguishes this from sibling search tools like search_items and get_deals by indicating compressed output, though it doesn't explicitly name the alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this versus the numerous sibling search tools (search_deals, search_persons, search_items, etc.) or when to prefer summarized over full results. The term 'summarized' implies usage but lacks explicit when/when-not direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.