Skip to main content
Glama
ckalima

Pipedrive MCP Server

pipedrive_create_activity

Create a Pipedrive activity by entering a subject and selecting a type, then add optional details such as due date, participants, and location.

Instructions

Create a new activity in Pipedrive. Subject and type are required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesActivity subject (required)
typeYesActivity type: call, meeting, task, deadline, email, lunch (required)
due_dateNoDue date (YYYY-MM-DD)
due_timeNoDue time (HH:MM)
durationNoDuration (HH:MM)
owner_idNoOwner user ID
deal_idNoLink to deal ID
lead_idNoLink to lead ID (UUID format)
person_idNoLink to person ID
org_idNoLink to organization ID
project_idNoLink to project ID
noteNoActivity notes (HTML supported)
doneNoMark as completed
busyNoShow as busy in calendar
priorityNoActivity priority (integer)
participantsNoActivity participants (person IDs)
attendeesNoExternal attendees (email addresses)
locationNoActivity location (structured object)
public_descriptionNoPublic description for guests
Behavior2/5

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

Annotations provide minimal behavioral info (readOnlyHint=false, destructiveHint=false). The description only states 'Create' but doesn't disclose creation behavior, side effects, success/error outcomes, or quotas. It adds little beyond annotations.

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?

The description is extremely concise at two sentences, with the first sentence stating the purpose and the second highlighting key requirements. Every word is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (19 parameters, nested objects, no output schema), the description is too brief. It lacks details on return value, validation rules, or behavioral context, making it insufficient for an agent to fully understand the tool's effects.

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?

With 100% schema description coverage, the schema already details all parameters. The description only reiterates that subject and type are required, which is already in the schema's required array. No extra semantic value is added.

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 verb 'Create' and the resource 'activity in Pipedrive', with required fields mentioned. It distinguishes from sibling tools like pipedrive_update_activity and pipedrive_list_activities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Beyond stating that subject and type are required, the description gives no guidance on when to use this tool vs alternatives (e.g., using pipedrive_update_activity for updates) or any prerequisites or limitations.

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/ckalima/pipedrive-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server