Skip to main content
Glama
comma-compliance

pipedrive-mcp

by comma-compliance
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

pipedrive_activities_list

List Pipedrive activities with filters and cursor pagination; filter by deal, person, organization, lead, user, owner, done status, sort field, and direction.

Instructions

List activities with filters and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doneNoFilter by done status
limitNoNumber of items per page (default 25, max 100)
cursorNoOpaque token from previous response to fetch the next page
org_idNoFilter by organization ID
deal_idNoFilter by deal ID
lead_idNoFilter by lead ID
sort_byNoField to sort by
user_idNoFilter by user ID
owner_idNoUser ID of the owner
person_idNoFilter by person ID
sort_directionNoSort direction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.1.1
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque token from previous response to fetch the next page"
    • addedInput schema / properties / deal_id / description
      Added value: +"Filter by deal ID"
    • addedInput schema / properties / done / description
      Added value: +"Filter by done status"
    • addedInput schema / properties / lead_id / description
      Added value: +"Filter by lead ID"
    • addedInput schema / properties / limit / description
      Added value: +"Number of items per page (default 25, max 100)"
    • addedInput schema / properties / org_id / description
      Added value: +"Filter by organization ID"
    • addedInput schema / properties / owner_id / description
      Added value: +"User ID of the owner"
    • addedInput schema / properties / person_id / description
      Added value: +"Filter by person ID"
    • addedInput schema / properties / sort_by / description
      Added value: +"Field to sort by"
    • addedInput schema / properties / sort_direction / description
      Added value: +"Sort direction"
    • addedInput schema / properties / user_id / description
      Added value: +"Filter by user ID"
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only mentions 'pagination' generically and says nothing about permissions, whether results are scoped to the authenticated user, default sort order, or what the response contains.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity contributes to the missing guidance rather than being a virtue in itself.

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?

For an 11-parameter list tool with no annotations and no output schema, the description is too thin. It leaves the agent without scope, default behavior, or result-format expectations that annotations or an output schema would otherwise supply.

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 description coverage is 100%, with every one of the 11 parameters documented inline (enums, ranges, defaults). The description adds nothing beyond the schema's own 'filters and pagination' framing, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (activities), so the core operation is unambiguous. However, it does nothing to distinguish itself from siblings like pipedrive_my_upcoming_activities or pipedrive_my_overdue_activities, which are also activity lists.

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?

The description gives no when-to-use guidance, no prerequisites, and no indication of when to prefer this over the scoped activity-list siblings. The agent must infer usage entirely from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools