Skip to main content
Glama
Sign In
Pipedrive MCP Server

Pipedrive MCP Server

by WillDent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search-deals

Read-onlyIdempotent

Search Pipedrive deals using title, notes, or custom fields. Retrieve deals matching your query with optional limit and pagination.

Instructions

Search Pipedrive deals by title, notes, or searchable custom fields.

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-deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is conveyed. Description adds that it searches by title, notes, or custom fields, but lacks details on pagination or exact matching behavior.

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?

Single sentence with no redundancy. Every word adds value given the context of a search tool.

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?

For a search tool with 3 parameters and no output schema, the description is brief. It lacks explanation of result format, pagination, and search behavior (e.g., partial match, case sensitivity), leaving gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%; description does not explain the 'term', 'limit', or 'cursor' parameters beyond what the schema provides. Agent may not understand what 'term' accepts or how pagination works.

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 Pipedrive deals by title, notes, or searchable custom fields.' It specifies the resource (deals) and the searchable fields, effectively differentiating from sibling tools like get-deals or search-persons.

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

Usage Guidelines3/5

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

The description implies usage for textual search but does not explicitly compare with siblings like get-deals (which might list or filter) or search-all. No guidance on when not to use or alternatives.

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

Deploy Server

Other Tools