Skip to main content
Glama

leads_list_archived

Retrieve a paginated list of archived leads, filtered by owner, person, or organization, to review or restore inactive leads.

Instructions

List archived leads with pagination and filtering options.

Returns a paginated list of archived leads. Archived leads are leads that have been moved out of the active Leads Inbox but not deleted or converted to deals.

Workflow tips:

  • Archived leads are sorted by creation time (oldest to newest)

  • Use owner_id to filter by lead owner

  • Use person_id or organization_id to filter by associated entities

  • filter_id takes precedence over other filters

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

  • Archived leads can be restored to active status using leads/update

Common use cases:

  • List all archived leads: {}

  • List archived leads for a specific owner: { "owner_id": 123 }

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

  • Review archived leads before deletion: { "limit": 50 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
owner_idNoFilter by owner (user) ID
person_idNoFilter by person ID
organization_idNoFilter by organization ID
filter_idNoID of the filter to use
sortNoField names and sorting mode (e.g., "title ASC, value DESC")
startNoPagination start
limitNoNumber of items to return
Behavior4/5

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

No annotations provided, so description carries full burden. It explains archived leads are moved out of active inbox but not deleted or converted, and lists sorting and pagination behavior. Lacks mention of permissions or side effects, but for a read-only list, this is sufficient.

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?

Well-structured with a summary, workflow tips, and common use cases. Front-loaded with the main action. A bit verbose but each section provides useful guidance; could be slightly more concise.

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?

No output schema, but the description explains what the tool returns (paginated list of archived leads), how to paginate and filter, and provides examples. Covers essential context for correct invocation.

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?

Schema covers all 7 parameters with descriptions. The description adds value by explaining filter_id precedence over others, default and max limit, and sorting order, which enhances agent understanding beyond the schema.

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 'List archived leads with pagination and filtering options.' It distinguishes from sibling tools like leads_list (active) and leads_search by specifically targeting archived leads.

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

Usage Guidelines5/5

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

Provides workflow tips including sorting order, filter precedence, pagination defaults, and common use cases with example parameters. It also mentions restoration via leads/update, guiding when not to use.

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