Skip to main content
Glama
Sign In
Pipedrive MCP Server

Pipedrive MCP Server

by ckalima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pipedrive_get_user

Read-onlyIdempotent

Retrieve specific user details by ID, enabling access to their profile data.

Instructions

Get details of a specific user by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "pipedrive_get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUser ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no behavioral context beyond what annotations offer, such as what 'details' include or any permission requirements.

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 (one sentence, 8 words) and front-loaded. Every word is necessary and contributes to the purpose.

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?

For a simple tool with one parameter and rich annotations, the description is adequate. It could be improved by briefly indicating common returned fields, but it is complete enough for an agent to understand the function.

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?

The schema has 100% coverage for the sole parameter 'id' with a clear description. The tool description does not add any extra meaning or context to the parameter.

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 'Get' and resource 'details of a specific user', with the key qualifier 'by ID'. It effectively distinguishes this tool from sibling 'list_users' which retrieves all users, and other 'get_' tools for different entities.

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

Usage Guidelines3/5

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

The description implies use when you have a user ID, but lacks explicit guidance on when not to use it (e.g., when you need to search users by other criteria, prefer 'list_users'). No alternatives are explicitly mentioned.

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