Skip to main content
Glama

deals_list_activities

List all activities linked to a deal, including calls, meetings, tasks, and emails. Filter by done status and paginate results.

Instructions

List all activities associated with a deal.

Returns all activities linked to a specific deal, including calls, meetings, tasks, emails, and deadlines.

Workflow tips:

  • Filter by done status to see completed or pending activities

  • Use start and limit for pagination

  • Exclude specific activity IDs if needed

  • Cached for 5 minutes for better performance

  • Activities are sorted by due date

Common use cases:

  • List all activities: { "id": 123 }

  • List pending activities: { "id": 123, "done": "0" }

  • List completed activities: { "id": 123, "done": "1" }

  • Paginated results: { "id": 123, "start": 0, "limit": 50 }

  • Exclude certain activities: { "id": 123, "exclude": "1,2,3" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal
startNoPagination start
limitNoNumber of items to return per page
doneNoFilter by activity status (0 = not done, 1 = done)
excludeNoComma-separated activity IDs to exclude
Behavior3/5

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

Discloses caching (5 minutes) and sorting by due date, which adds value beyond the schema. No annotations were provided, so the description carries the burden. However, it does not cover error handling, permissions, or rate limits.

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?

Extremely concise with a clear structure: purpose statement, then details, workflow tips, and common use cases. Every sentence is informative with no redundancy.

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 all parameters with examples, caching, sorting, and result types. While no output schema exists, the description does not detail the response structure (e.g., array of activities), but it is sufficient for typical usage.

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 coverage is 100%, but the description adds meaning with examples (e.g., done='0' for pending, comma-separated exclude IDs) and explains the activity types (calls, meetings, tasks, etc.), extending beyond bare schema definitions.

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?

Clearly states 'List all activities associated with a deal.' Identifies the specific resource (deal) and action (listing), distinguishing it from sibling tools like activities_list or activities_list_by_deal.

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 and common use cases with parameter examples (done, start, limit, exclude). Clearly indicates when to use each filter, though does not explicitly mention when not to use this tool or alternatives.

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