Skip to main content
Glama

deals_add_participant

Add a person as a participant to an existing deal, enabling you to include decision makers, influencers, or stakeholders beyond the primary contact.

Instructions

Add a participant (person) to a deal.

Participants are persons who are involved in the deal beyond the primary contact.

Workflow tips:

  • Use persons/search to find person IDs

  • Person must exist in Pipedrive

  • Deal can have multiple participants

  • Different from the main person_id on the deal

Common use cases:

  • Add decision maker: { "id": 123, "person_id": 456 }

  • Add influencer: { "id": 789, "person_id": 101 }

  • Add stakeholder: { "id": 234, "person_id": 567 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal
person_idYesID of the person to add as a participant
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as idempotency, error states, or permission requirements. The burden falls entirely on the description, which only covers the basic function.

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?

Well-structured with clear sections (description, workflow tips, common use cases). Concise without unnecessary words.

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?

No output schema is present. The description does not explain the return value or behavior when adding a duplicate participant. However, for a simple add operation, the context is minimally adequate.

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% (both parameters described). The description adds no extra meaning beyond the schema, meeting the baseline.

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's action ('Add a participant') and the resource ('deal'). It distinguishes participants from the primary contact and differentiates from sibling tools like 'deals_add_follower' or 'deals_add_product'.

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 (use persons/search, person must exist) and common use cases with example objects. Lacks explicit exclusions or alternatives but gives clear context.

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