Pipedrive MCP

update_note

Modify the content of an existing note and pin or unpin it from a deal. Content supports HTML formatting.

Instructions

Edita o conteúdo de uma nota existente e/ou pina/despina no deal. O conteúdo suporta HTML.

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": {
      "note_id": "<note_id>"
    },
    "name": "update_note"
  }
}

Input Schema

Name	Required	Description
`pinned`	No	true = pinar nota no deal, false = despinar
`content`	No	Novo conteúdo da nota (suporta HTML)
`note_id`	Yes	ID da nota a editar

Schema Changelog

Changes observed during successful MCP inspections.

First observedv6.1.2Jul 12, 2026

TDQS

A3.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 must fully disclose behavioral traits. It mentions editing and pinning but omits details about permissions, side effects (e.g., notifications), or reversibility. The mutation nature is implied but not elaborated.

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?

The description is a single concise sentence that front-loads the primary action. Every word contributes meaning, with 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?

For a tool with 3 parameters and no output schema or annotations, the description adequately explains core functionality. However, it lacks details on default behavior when optional parameters are omitted, potential errors, or return values, leaving gaps for an agent.

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 parameters are already documented. The description adds minimal extra by confirming HTML support for content and clarifying that pin/unpin relates to a deal. This is consistent with the schema but does not significantly enhance understanding.

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 the verb 'Edita' (edits) and the resource 'nota' (note), with specific actions: editing content and pinning/unpinning in a deal. It distinguishes from sibling tools like create_note and list_deal_notes by focusing on modification of existing 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 usage for updating existing notes but does not explicitly state when to use this tool versus alternatives such as create_note or list_deal_notes. No exclusions or prerequisites are mentioned.

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