Skip to main content
Glama

notes_add_comment

Add comments to Pipedrive notes to enable threaded discussions, track feedback, and provide updates on deals and activities.

Instructions

Add a new comment to a note.

Creates a comment on an existing note, allowing for threaded discussions.

Workflow tips:

  • content is required

  • Comments are added by the authenticated user

  • Use this to create conversations around notes

  • Comments help track discussions and decisions

Common use cases:

  • Add feedback: { "id": 123, "content": "Agreed, let's proceed with this approach" }

  • Ask questions: { "id": 456, "content": "Can we clarify the timeline?" }

  • Provide updates: { "id": 789, "content": "Completed this action item" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the note to add comment to (required)
contentYesContent of the comment (required)
Behavior3/5

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

No annotations provided, so description carries the burden. It mentions 'authenticated user' but lacks details on response, idempotency, or error conditions.

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?

Well-structured with main purpose, workflow tips, and common use cases. Every sentence adds value without redundancy.

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

Completeness4/5

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

Sufficient for a simple create tool with two required parameters. Could mention return value or error handling, but overall complete.

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 covers parameters fully; description adds example JSON objects but does not add meaning beyond schema's type and description.

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 'add' and resource 'comment to a note', and differentiates from sibling tools like notes_update_comment and notes_create. It mentions 'threaded discussions', implying hierarchy.

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

Usage Guidelines4/5

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

Provides workflow tips and common use cases with examples, but does not explicitly state when not to use or compare to alternatives like notes_update_comment.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iamsamuelfraga/mcp-pipedrive'

If you have feedback or need assistance with the MCP directory API, please join our Discord server