Skip to main content
Glama

activity_types_bulk_delete

Delete multiple custom activity types in a single operation by providing comma-separated IDs. Clean up unused activity types quickly.

Instructions

Delete multiple activity types in bulk.

Marks multiple activity types as deleted in a single operation. Only custom activity types can be deleted.

Workflow tips:

  • Provide comma-separated activity type IDs

  • Only custom activity types can be deleted (is_custom_flag = true)

  • More efficient than deleting one at a time

  • All specified types are marked as inactive in one request

Common use cases:

  • Remove multiple custom types: { "ids": "12,13,14" }

  • Bulk cleanup: { "ids": "15,16,17,18" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated activity type IDs to delete (e.g., "1,2,3")
Behavior4/5

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

No annotations provided, so description carries full burden. It clearly explains the operation marks types as deleted/inactive and is a single request. No hidden side effects mentioned, but the core behavior is transparent.

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?

Description is clear and structured with a main paragraph and separate workflow tips/common use cases. Could be slightly more concise, but it is well-organized and front-loaded.

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?

Given the tool has only one parameter and no output schema, the description fully covers what the tool does, constraints (custom types only), and how to provide input. Examples make it complete.

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% and schema already describes the 'ids' parameter as comma-separated. Description adds usage examples but does not add significant new meaning beyond 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 it deletes multiple activity types in bulk, marking them as deleted. It distinguishes itself from single delete (activity_types_delete) and other bulk operations on different resources.

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?

Workflow tips provide explicit instructions: comma-separated IDs, only custom types, efficiency benefit. Common use cases illustrate typical inputs. Does not explicitly compare to alternatives but gives enough context for proper 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