Skip to main content
Glama

channels_receive_message

Add an incoming message to a Pipedrive conversation with required fields like id, channel_id, sender_id, conversation_id, message, status, and created_at.

Instructions

Add an incoming message to a conversation in Pipedrive.

This endpoint requires the Messengers integration OAuth scope and the Messaging manifest ready for the Messaging app extension.

Required fields:

  • id: ID of the message

  • channel_id: ID of the channel the message was sent to

  • sender_id: ID of the message sender

  • conversation_id: ID of the conversation this message belongs to

  • message: Content of the message

  • status: Status of the message (e.g., sent, delivered, read)

  • created_at: When the message was created (ISO 8601 format)

Optional fields:

  • reply_by: When a reply is expected by (ISO 8601 format)

  • conversation_link: Link to the conversation in the provider system

  • attachments: Array of message attachments

Example: { "id": "e283f878-7ef9-4294-8e5c-04a7d003fd92", "channel_id": "a8aa4db0-91bb-4e90-b9c0-0c6291307e2f", "sender_id": "5d4bd467-d847-4088-ae43-0c7614233bab", "conversation_id": "063ffa46-831c-4027-a04c-b65e17f077b7", "message": "This is a message", "status": "sent", "created_at": "2022-03-01T07:58:35.449Z", "reply_by": "2022-03-01T07:58:35.449Z", "conversation_link": "http://my-server.com/conversations/063ffa46-831c-4027-a04c-b65e17f077b7", "attachments": [ { "id": "b0369d1d-6b6a-4293-88b9-e2924782d47e", "type": "image/png", "name": "Image Name", "size": 600, "url": "http://my-server.com/images/b0369d1d-6b6a-4293-88b9-e2924782d47e.png", "preview_url": "http://my-server.com/images/b0369d1d-6b6a-4293-88b9-e2924782d47e.preview.png" } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the message (required)
channel_idYesID of the channel the message was sent to (required)
sender_idYesID of the message sender (required)
conversation_idYesID of the conversation this message belongs to (required)
messageYesContent of the message (required)
statusYesStatus of the message (e.g., sent, delivered, read) (required)
created_atYesWhen the message was created in ISO 8601 format (required)
reply_byNoWhen a reply is expected by in ISO 8601 format
conversation_linkNoLink to the conversation in the provider system
attachmentsNoArray of message attachments
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a write operation ('add') but does not disclose idempotency, side effects, or error handling. Prerequisites are given, but behavioral details are minimal.

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

Conciseness4/5

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

The description is well-structured with a clear first sentence, prerequisites, field lists, and an example. It is appropriately detailed without being verbose, though it could be slightly more concise.

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?

The tool has no output schema, yet the description does not explain the return value or response format. It covers prerequisites and fields well but lacks information on success/error responses, rate limits, or idempotency. Given the complexity (10 params, no output schema), it falls short of 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 coverage is 100%, so parameters are fully described in the schema. The description repeats the field list and groups required/optional but adds no new semantics beyond the schema. An example is provided, which helps, but the schema already does the heavy lifting.

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 tool adds an incoming message to a conversation, with a specific verb ('add') and resource ('message'). This distinguishes it from sibling tools, many of which are CRUD for other entities like activities, deals, etc.

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 specifies required OAuth scope and messaging manifest prerequisites. It does not explicitly mention when not to use or alternatives, but the context is clear for this specific action.

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