Skip to main content
Glama

users_create

Create a new Pipedrive user. Requires admin permissions and unique email. New users receive an activation email.

Instructions

Add a new user to the company.

Creates a new user account in the Pipedrive company. Requires admin permissions.

Workflow tips:

  • Email is required and must be unique

  • User will receive an activation email

  • New users are active by default

  • Name can be provided or will be derived from email

Common use cases:

  • Add new team member: { "name": "John Doe", "email": "john@company.com" }

  • Create inactive user: { "name": "Jane Smith", "email": "jane@company.com", "active_flag": false }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the user
emailYesEmail address of the user (must be unique)
active_flagNoWhether the user is active (default: true)
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses need for admin permissions, activation email sending, default active status, and that name can be derived from email. Does not mention rate limits or billing impact, but covers key behavioral traits.

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 purpose, admin note, bulleted workflow tips, and example use cases. Every sentence adds value, and the format is easy to scan. No redundant or vague statements.

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?

Covers creation behavior, constraints, and typical usage patterns. Lacks details on return value or error cases, but for a tool with no output schema and clear parameters, this is sufficient. Could mention response includes user object.

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?

Schema coverage is 100%; each parameter has a description. The description adds value by noting email uniqueness requirement, derivation of name from email, and providing example JSON objects, which enhance understanding 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?

Clearly states 'Add a new user to the company' and 'Creates a new user account in the Pipedrive company', distinguishing it from sibling tools like users_update or users_get. The verb-resource pair is specific and unambiguous.

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 (email uniqueness, activation email, default active, name derivation) and common use cases with examples. Does not explicitly mention when not to use or alternatives, but the context is sufficient for a create operation.

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