Pipedrive MCP Server

get_notes

Retrieve notes from Pipedrive CRM with filtering options for users, deals, persons, organizations, and pinned status to organize customer relationship data.

Instructions

Get a list of notes from Pipedrive

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_notes"
  }
}

Input Schema

Name	Required	Description
`start`	No	Pagination start (default: 0)
`limit`	No	Number of items to return (default: 100, max: 500)
`user_id`	No	Filter by user ID
`deal_id`	No	Filter by deal ID
`person_id`	No	Filter by person ID
`org_id`	No	Filter by organization ID
`pinned_to_deal_flag`	No	Filter by pinned to deal flag
`pinned_to_person_flag`	No	Filter by pinned to person flag
`pinned_to_organization_flag`	No	Filter by pinned to organization flag

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 1, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden of behavioral disclosure. It does not indicate this is read-only/safe, does not explain default behavior when filters are omitted (returns all notes?), pagination behavior beyond the schema defaults, or any rate limiting concerns for large datasets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the single sentence is not verbose, it suffers from under-specification rather than efficient precision. Given the lack of annotations and output schema, the description should be front-loaded with more behavioral context rather than being so terse.

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

Completeness2/5

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

With 9 parameters and no output schema or annotations, the description leaves significant gaps. It fails to explain the relationship between the various filter parameters (user_id, deal_id, person_id, org_id) and their combinability, nor does it address return values or error conditions expected from this complex query tool.

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 description coverage is 100%, so the schema adequately documents all 9 parameters (pagination, entity filters, pinned flags). The description adds no parameter-specific guidance, but the baseline score of 3 applies when schema coverage is high.

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

Purpose3/5

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

The description states the basic action (Get a list) and resource (notes from Pipedrive), but fails to distinguish from sibling tool 'get_note' (singular). It borders on tautology by restating the tool name without clarifying when to use the plural/list version versus the singular fetch.

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 guidance provided on when to use this tool versus 'get_note' or other sibling tools. No mention of prerequisite conditions (e.g., needing specific IDs for filtering) or when to apply which filters among the 9 available parameters.

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