Skip to main content
Glama
bratland

Pipedrive MCP Server

by bratland

get_deal

Retrieve a specific Pipedrive deal by its ID to access CRM data such as contact details, pipeline status, and activity information.

Instructions

Get a specific deal by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDeal ID

Implementation Reference

  • The PipedriveClient.getDeal method which makes the actual API request for a specific deal.
    async getDeal(id: number): Promise<PipedriveResponse<Deal>> {
      return this.handleRequest<Deal>(
        this.client.get(`/deals/${id}`)
      );
    }
  • The tool definition (schema) for 'get_deal', detailing input requirements.
    {
      name: 'get_deal',
      description: 'Get a specific deal by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Deal ID',
          },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description omits error handling (e.g., invalid ID), return structure, authentication requirements, or rate limits. This leaves significant behavioral gaps for a data retrieval tool.

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?

The description is extremely concise at five words with the main action front-loaded. However, given the lack of annotations and the complex sibling landscape, this brevity crosses into under-specification. It wastes no words but omits necessary context.

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 presence of numerous sibling tools (get_deals, search_deals, etc.) and the absence of both output schema and annotations, the description is incomplete. It fails to clarify the distinction between retrieval by specific ID versus querying or bulk listing, which is essential for tool selection.

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% for the single 'id' parameter, which is documented as 'Deal ID' in the schema. The description references the parameter implicitly ('by ID') but adds no additional semantic context (e.g., expected format, where to find valid IDs) beyond the schema baseline.

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?

The description provides a clear verb ('Get'), resource ('deal'), and scope ('specific...by ID'), meeting the basic requirements for purpose clarity. However, it fails to explicitly differentiate from sibling tools like 'get_deals' or 'search_deals', which is critical given the presence of multiple deal-retrieval tools.

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 contains no guidance on when to use this singular lookup versus the plural 'get_deals', the filtered 'get_current_quarter_deals', or the flexible 'search_deals'. Agents cannot determine selection criteria from the description alone.

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

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