Skip to main content
Glama

roles_create

Add a new role to your Pipedrive company, with optional parent role for hierarchical organization.

Instructions

Add a new role to the company.

Creates a new role with optional parent role for hierarchy. Requires admin permissions.

Workflow tips:

  • Name is required and should be unique

  • Parent role creates hierarchy

  • New roles start with default permissions

  • Use roles/add_role_setting to configure permissions

Common use cases:

  • Create top-level role: { "name": "Sales Team" }

  • Create sub-role: { "name": "Junior Sales", "parent_role_id": 123 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the role
parent_role_idNoID of the parent role (optional, for hierarchy)
Behavior4/5

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

Discloses admin permissions, optional parent role for hierarchy, and that new roles start with default permissions. No annotations provided, so description carries full burden and does well.

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 sections, clear and informative. Could be slightly more concise but every sentence adds value.

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, and description does not mention what is returned (e.g., created role object). For a creation tool, return value is important context.

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%, but description adds value by noting name uniqueness, optional parent_role_id for hierarchy, and providing example JSON payloads.

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 new role to the company' with specific verb and resource. Examples differentiate from sibling tools like roles_update or roles_delete.

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 and common use cases, including admin permission requirement. Mentions related tool for permissions but lacks explicit 'when not to use' or alternatives.

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