Skip to main content
Glama
iamsamuelfraga

Pipedrive MCP Server

by iamsamuelfraga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

webhooks_list

Retrieve all webhooks configured in your Pipedrive account, including active and inactive subscriptions. Use this to audit endpoints, debug delivery issues, or get webhook IDs for updates.

Instructions

Get all webhooks configured for the company.

Returns a list of all webhooks that have been created in Pipedrive, including:

  • Active and inactive webhooks

  • Event triggers (action + object combinations)

  • Subscription URLs

  • Authentication settings

  • Last delivery information

Note: Webhook data is always fetched fresh (no caching) to ensure you see the current state.

Common use cases:

  • List all active webhooks: Review current webhook configurations

  • Audit webhook endpoints: Check which URLs are receiving notifications

  • Debug webhook issues: View last delivery time and HTTP status

  • Manage webhooks: Get webhook IDs before updating or deleting

Event combinations explained:

  • event_action: added, updated, deleted, merged, or * (all)

  • event_object: activity, deal, person, organization, note, pipeline, product, stage, user, or * (all)

  • Examples: "added.deal", "updated.person", "deleted.organization", "." (all events)

Webhook fields returned:

  • id: Webhook ID

  • subscription_url: The URL that receives webhook notifications

  • event_action & event_object: The trigger combination

  • is_active: Whether the webhook is currently active

  • add_time: When the webhook was created

  • last_delivery_time: Last successful delivery timestamp

  • last_http_status: HTTP status code from last delivery attempt

  • version: Webhook API version (1.0 or 2.0)

  • name: Optional webhook name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that data is fetched fresh (no caching) and details all returned fields. No contradictions.

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 well-structured with bullet points and sections, front-loaded with the main purpose. It is appropriately detailed without being verbose.

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

Completeness5/5

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

Given no parameters and no output schema, the description provides extensive information about return fields, use cases, and event combinations, making it complete for its purpose.

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?

The input schema has zero parameters, so schema coverage is 100%. The description adds value by explaining the output fields and event combinations, exceeding the baseline of 3.

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 'Get all webhooks configured for the company.' It specifies the resource and action, and distinguishes from siblings like webhooks_create and webhooks_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?

The description provides explicit use cases (list active webhooks, audit endpoints, debug issues, manage webhooks) and explains event combinations, but does not explicitly exclude when not to use the tool.

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