Skip to main content
Glama

notes_update_comment

Revise the text of a specific comment on a Pipedrive note by providing the note ID and comment UUID.

Instructions

Update an existing comment on a note.

Modifies the content of a specific comment on a note.

Workflow tips:

  • Both note id and comment_id are required

  • comment_id is a UUID, not a number

  • Only the content can be updated

  • Use notes_list_comments to find the comment_id

Common use cases:

  • Fix typos: { "id": 123, "comment_id": "uuid-here", "content": "Corrected text" }

  • Add details: { "id": 456, "comment_id": "uuid-here", "content": "Updated with more info" }

  • Clarify response: { "id": 789, "comment_id": "uuid-here", "content": "Revised answer" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the note (required)
comment_idYesUUID of the comment to update (required)
contentYesNew content of the comment (required)
Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It states 'Modifies the content' indicating mutation, but lacks details on idempotency, permissions, side effects, or return value. The agent is left without information on what the response looks like or error cases.

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 concise and well-structured: a clear purpose statement, followed by bullet-style workflow tips and common use cases with JSON examples. Every sentence adds value, and the formatting aids readability.

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?

For a simple tool with 3 parameters and no output schema, the description covers the what, required inputs, constraints, and examples. However, it is missing information about return format or error handling, which would make it fully complete.

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

Parameters4/5

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

The input schema has 100% coverage with descriptions, but the description adds value by clarifying that comment_id is a UUID (not a number), that both IDs are required for identification, and that only content is mutable. The provided examples demonstrate real usage, adding practical 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 states the tool updates an existing comment on a note with the specific verb 'Update'. It distinguishes from sibling tools like notes_add_comment and notes_delete_comment by specifying that only content can be modified.

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?

The description provides workflow tips on required IDs, UUID format, and the constraint that only content can be updated. It references notes_list_comments for finding comment_id, giving clear context for use, but does not explicitly state when not to use this tool (e.g., for adding or deleting comments).

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