Skip to main content
Glama

persons_bulk_delete

Delete multiple person records in one bulk operation for data cleanup, duplicate removal, and GDPR compliance. Irreversible; verify IDs before proceeding.

Instructions

Delete multiple persons in bulk.

Efficiently deletes multiple person records in a single operation. This is useful for:

  • Data cleanup and maintenance

  • Removing duplicate records

  • Batch operations after data imports

  • CRM hygiene improvements

  • GDPR and data retention compliance

WARNING: This action is irreversible. All specified persons will be permanently deleted, including:

  • Person data and custom fields

  • Associated notes (if configured)

  • Follow relationships

  • Activity history (may be preserved depending on settings)

Best practices:

  1. Always verify the IDs before deletion

  2. Consider exporting data as backup

  3. Check if persons have active deals

  4. Review organization associations

  5. Ensure you have proper permissions

The 'ids' parameter should be a comma-separated string of person IDs. Example: "123,456,789" will delete persons with IDs 123, 456, and 789.

Rate limits may apply for very large deletions. Consider batching if deleting hundreds or thousands of records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated list of person IDs to delete (e.g., "123,456,789")
Behavior5/5

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

Despite no annotations, the description fully discloses irreversibility, data deleted (custom fields, notes, follow relationships), activity handling, rate limits, and permission requirements. Comprehensive 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections, bullet points, and warnings. Length is justified by complexity of bulk deletion, but could be slightly more concise.

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?

Covers prerequisites, side effects (what is deleted), best practices, and rate limits. No output schema, but description explains return behavior adequately.

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 description mostly restates schema (comma-separated IDs). Adds example and usage context, but does not significantly enhance 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?

Clearly states 'Delete multiple persons in bulk' and lists specific use cases (data cleanup, duplicates, GDPR). Distinguishes from sibling tools like persons_delete by specifying bulk operation.

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 explicit best practices (verify IDs, backup, check deals, permissions) and warnings (irreversible, rate limits). Implies when to use but does not explicitly exclude alternative single-delete 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