Skip to main content
Glama
bit2beat

Bitrix24 MCP server

b24_crm_delete

Remove a CRM entry in Bitrix24 using the record's unique identifier.

Instructions

Elimina un registro CRM por ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityNo
entity_type_idNo
idYes
webhook_urlNo

Implementation Reference

  • The actual handler function that executes the delete logic. It calls the Bitrix24 REST API using `${base}.delete` to remove a CRM record by ID, and returns success confirmation.
    export async function crmDelete({ entity, entity_type_id, id, webhook_url }) {
      const client = new Bitrix24Client(resolveWebhook(webhook_url));
      const { base, extra } = resolveMethod(entity, entity_type_id);
      await client.call(`${base}.delete`, { id, ...extra });
      return { entity: entity || `SPA_${entity_type_id}`, portal: client.portal, deleted_id: id, success: true };
    }
  • Zod schema defining input validation for b24_crm_delete: entity (optional), entity_type_id (optional integer), id (required string or number), webhook_url (optional URL).
    export const crmDeleteSchema = z.object({
      entity: z.string().optional(),
      entity_type_id: z.number().int().optional(),
      id: z.union([z.string(), z.number()]),
      webhook_url: z.string().url().optional(),
    });
  • index.js:125-127 (registration)
    Registration of the 'b24_crm_delete' tool on the MCP server with description, schema, and wrapped handler.
    server.tool('b24_crm_delete',
      'Elimina un registro CRM por ID.',
      crmDeleteSchema.shape, wrap(crmDelete));
  • index.js:13-16 (registration)
    Import of crmDeleteSchema and crmDelete from src/tools/crm.js into the main server registration file.
      crmDeleteSchema, crmDelete,
      crmFieldsSchema, crmFields,
      timelineAddSchema, timelineAdd,
    } from './src/tools/crm.js';
Behavior2/5

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

Without annotations, the description should disclose behavioral traits like permanence, cascading effects, or authorization needs. It only states the basic operation, leaving critical behavior unspecified.

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?

The description is a single, efficient sentence without fluff. However, it lacks structure (e.g., bullet points) that could aid readability, but the conciseness is appropriate for a simple operation.

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

Completeness1/5

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

Given four parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain parameter roles, return values, or side effects, making the tool risky for autonomous use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to parameters (entity, entity_type_id, webhook_url). The agent must guess what these fields represent.

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 the action (delete) and the resource (CRM record) via a specific identifier (ID), distinguishing it from sibling tools like create, update, or get.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, nor any prerequisites, permissions, or exclusions. The agent must infer context from the tool name alone.

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/bit2beat/bitrix24-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server