Skip to main content
Glama
Sign In
Pipedrive MCP Server

Pipedrive MCP Server

by ckalima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pipedrive_create_note

Create a Pipedrive note with required content and link it to a deal, person, organization, or lead.

Instructions

Create a new note in Pipedrive. Content is required. Link to a deal, person, organization, or lead.

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": {
      "content": "<content>"
    },
    "name": "pipedrive_create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_idNoLink to organization ID
contentYesNote content (required, HTML supported)
deal_idNoLink to deal ID
lead_idNoLink to lead ID (UUID format)
person_idNoLink to person ID
pinned_to_deal_flagNoPin note to deal
pinned_to_person_flagNoPin note to person
pinned_to_organization_flagNoPin note to organization

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already indicate non-readOnly and non-destructive. The description adds that content is required and linking is possible, but does not disclose potential side effects, permissions, or return values.

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?

Two sentences, front-loaded with the purpose, and no wasted words. Efficient and to the point.

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?

Covers creation and linking but omits mention of return value (e.g., note ID), pin flags, content length limits, or other constraints. Adequate but not comprehensive.

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 has 100% coverage with detailed descriptions for each parameter. The description reiterates required content and linking options but adds no new meaning beyond the 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?

The description clearly states 'Create a new note in Pipedrive', specifying the verb and resource. It distinguishes from sibling tools (e.g., create_deal, create_activity) by focusing on notes.

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 when to use (create note) and notes required content. However, it does not explicitly state when not to use this tool (e.g., for updating notes) or compare with alternatives like pipedrive_update_note.

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