Skip to main content
Glama

deals_add_follower

Add a user as a follower to a deal to enable them to receive notifications and track progress.

Instructions

Add a follower to a deal.

Followers receive notifications about deal updates and can track the deal's progress.

Workflow tips:

  • Use users/list to get user IDs

  • User must exist in the Pipedrive account

  • Follower receives notifications for deal changes

  • Cannot add same follower twice

Common use cases:

  • Add team member: { "id": 123, "user_id": 456 }

  • Add manager for oversight: { "id": 789, "user_id": 10 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal
user_idYesID of the user to add as a follower
Behavior3/5

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

Discloses that followers receive notifications and that duplicates are rejected, but lacks details on auth, rate limits, or idempotency. With no annotations, description carries burden and is adequate but not exhaustive.

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?

Description is well-organized with sections, examples, and tips, though slightly verbose; still effective and front-loaded with key action.

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?

Given low complexity (2 params, no output schema, no nested objects), description covers purpose, constraints, and common scenarios. Lacks response format but adequate for a simple mutation tool.

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% and description adds no new meaning beyond the schema's field descriptions, earning baseline 3.

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?

Description clearly states 'Add a follower to a deal' with specific verb and resource, and distinguishes from siblings like 'deals_remove_follower' and 'persons_add_follower' by focusing on deal followers.

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 users/list, user must exist, cannot add same follower twice) and examples, but does not explicitly state when not to use this tool.

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