Skip to main content
Glama
ckalima

Pipedrive MCP Server

by ckalima

pipedrive_list_activities

Read-onlyIdempotent

Filter and retrieve Pipedrive activities by owner, deal, person, organization, or completion status to manage your CRM tasks.

Instructions

List activities from Pipedrive with optional filtering by owner, deal, person, organization, type, or completion status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated activity IDs to fetch (max 100)
doneNoFilter by completion (true=done, false=pending)
limitNoNumber of items (1-100)
cursorNoCursor for pagination
org_idNoFilter by organization ID
deal_idNoFilter by deal ID
lead_idNoFilter by lead ID (UUID format)
sort_byNoField to sort by
owner_idNoFilter by owner user ID
filter_idNoFilter by saved filter ID
person_idNoFilter by person ID
updated_sinceNoFilter activities updated after this time (RFC3339 format)
updated_untilNoFilter activities updated before this time (RFC3339 format)
include_fieldsNoInclude additional data in response
sort_directionNoSort direction

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv2.4.0
    • removedInput schema / properties / end_date
      Removed value: -{
      -  "description": "Filter to date (YYYY-MM-DD)",
      -  "type": "string"
      -}
    • removedInput schema / properties / project_id
      Removed value: -{
      -  "description": "Filter by project ID",
      -  "type": "number"
      -}
    • removedInput schema / properties / start_date
      Removed value: -{
      -  "description": "Filter from date (YYYY-MM-DD)",
      -  "type": "string"
      -}
    • removedInput schema / properties / type
      Removed value: -{
      -  "description": "Filter by type (call, meeting, task, etc.)",
      -  "type": "string"
      -}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so safety is clear. Description adds no behavioral traits beyond what annotations provide, but does not contradict them. It adequately conveys that this is a safe list operation.

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?

Single sentence, no wasted words. Front-loaded with action and resource, then lists key capabilities efficiently.

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?

No output schema, but the description covers the main purpose and filtering options. For a list tool with 15 parameters, the description is reasonably complete, though it omits details like pagination behavior (handled by schema). Overall adequate.

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% with each parameter described. Description only mentions a subset of filter parameters (owner, deal, etc.) but does not add meaning beyond what the schema provides. Baseline 3 is appropriate.

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 verb 'List' and resource 'activities', and lists key filtering options. It distinguishes from sibling tools like pipedrive_get_activity (single item) and pipedrive_list_tasks (different resource).

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?

Description implies usage for listing activities with filters, but does not explicitly say when to use vs alternatives (e.g., get_activity for specific, list_archived_activities for archived). Context is clear but no exclusions stated.

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