Skip to main content
Glama

deals_list_archived

Retrieve a paginated list of archived deals, with filters by status, user, stage, person, and more.

Instructions

List archived deals with pagination and filtering options.

Returns a paginated list of archived deals. Archived deals are deals that have been removed from active pipelines.

Workflow tips:

  • Use same filters as deals/list (status, stage_id, user_id, person_id, org_id, etc.)

  • Filter by user_id to see archived deals by specific user

  • Combine with filter_id to use pre-configured Pipedrive filters

  • Use start/limit for pagination (default limit: 100, max: 500)

  • Useful for historical analysis and cleanup

Common use cases:

  • List all archived deals: {}

  • List archived deals by user: { "user_id": 123 }

  • List archived deals in a specific stage: { "stage_id": 5 }

  • List archived deals for a person: { "person_id": 456 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by deal status
stage_idNoFilter by stage ID
user_idNoFilter by user (owner) ID
person_idNoFilter by person ID
org_idNoFilter by organization ID
pipeline_idNoFilter by pipeline ID
filter_idNoID of the filter to use
sortNoField to sort by (e.g., title, value, stage_id)
owned_by_youNoFilter deals owned by the authorized user (1 = yes, 0 = no)
startNoPagination start
limitNoNumber of items to return
Behavior4/5

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

Explains that archived deals are removed from active pipelines and describes pagination limits (default 100, max 500). No side effects or destructive actions are involved, so transparency is adequate.

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-organized with a clear first sentence, explanatory context, and bullet-style workflow tips and examples. No wasted words.

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?

Covers pagination and filtering adequately for a list endpoint. Lacks explicit return structure, but the presence of sibling deals_list and typical paginated list conventions make up for it.

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 schema already describes all 11 parameters (100% coverage). The description adds value by grouping filters, mentioning compatibility with deals/list, and explaining filter_id usage and pagination limits.

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 it lists archived deals with pagination and filtering, distinguishing it from related sibling tools like deals_list (active deals) and deals_get_archived_deals_timeline.

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?

Provides workflow tips mentioning compatibility with deals/list filters and explicit JSON examples for common use cases. However, it does not explicitly state when to avoid using this 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