Retrieve all deal field definitions, including custom fields, to understand the data structure for Pipedrive deals. Use pagination parameters to manage large lists.
List all deal field definitions, including custom fields. Essential for understanding deal data structure.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of items (1-100) | |
| cursor | No | Cursor for pagination (from previous response) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v2.4.0Input schema / properties / cursorAdded value: +{
+ "description": "Cursor for pagination (from previous response)",
+ "type": "string"
+}Input schema / properties / limit / descriptionPrevious value: -"Number of items"New value: +"Number of items (1-100)"Input schema / properties / startRemoved value: -{
- "description": "Pagination offset",
- "type": "number"
-}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds the detail about including custom fields, which is useful but does not disclose additional behavioral traits beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that conveys the key information. It front-loads the action and specificity. Could be slightly expanded but is efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (2 parameters, no output schema, annotations covering safety), the description adequately conveys what the tool does and its purpose. It is sufficiently complete for an agent to understand when to use it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%. Both parameters (cursor and limit) are described in the schema. The description does not add additional meaning beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'list', the resource 'deal field definitions', and scope 'all, including custom fields'. It distinguishes this tool from sibling listing tools (e.g., list_organization_fields) by specifying deal fields.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Essential for understanding deal data structure' provides context for when to use this tool. However, it does not explicitly state when not to use it or mention alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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