Skip to main content
Glama

activities_bulk_delete

Delete multiple activities in a single request. Remove up to 100 completed, outdated, or duplicate activities permanently.

Instructions

Delete multiple activities in a single request.

This endpoint allows you to delete up to 100 activities at once by providing an array of activity IDs.

Workflow tips:

  • Maximum 100 activities per request

  • All activities must exist and be accessible to the user

  • Deletion is permanent and cannot be undone

  • Failed deletions for individual activities won't stop others from being deleted

Common use cases:

  • Clean up completed activities in bulk

  • Remove outdated or duplicate activities

  • Archive old activities by deleting them

Example: { "ids": [123, 456, 789] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesArray of activity IDs to delete (max 100)
Behavior5/5

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

Despite no annotations, the description fully discloses critical behavior: deletion is permanent and cannot be undone, and failed deletions for individual activities do not block others. This is transparent for a destructive operation.

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-structured: brief purpose, bulleted workflow tips, list of use cases, and a JSON example. Every sentence adds value; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, destructive bulk operation, the description covers constraints (max 100, permanence), permissions (must be accessible), error behavior (partial failures), and usage context. No output schema needed; the action outcome is implicit.

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?

Schema coverage is 100% with a clear description of the 'ids' parameter. The description adds an example but does not provide new semantic meaning beyond the schema. Per rules, baseline is 3.

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 'Delete multiple activities in a single request', specifying the verb (delete) and resource (multiple activities). It distinguishes from siblings like 'activities_delete' (single) and other bulk delete tools.

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 explicit workflow tips: max 100 per request, all IDs must exist and be accessible, permanent deletion, and partial failure behavior. Lists common use cases, helping the agent decide when to use 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