Skip to main content
Glama
bit2beat

Bitrix24 MCP server

b24_crm_update

Update fields of an existing CRM record by providing its ID and the fields to modify.

Instructions

Actualiza campos de un registro CRM existente.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityNo
entity_type_idNo
idYes
fieldsYesCampos a actualizar
paramsNo
webhook_urlNo

Implementation Reference

  • index.js:121-123 (registration)
    Registration of the 'b24_crm_update' tool with description, schema, and handler
    server.tool('b24_crm_update',
      'Actualiza campos de un registro CRM existente.',
      crmUpdateSchema.shape, wrap(crmUpdate));
  • Zod schema defining input validation for the update tool: entity/entity_type_id, id, fields to update, optional params and webhook_url
    export const crmUpdateSchema = z.object({
      entity: z.string().optional(),
      entity_type_id: z.number().int().optional(),
      id: z.union([z.string(), z.number()]),
      fields: z.record(z.any()).describe('Campos a actualizar'),
      params: z.record(z.any()).optional(),
      webhook_url: z.string().url().optional(),
    });
  • Handler function that executes the CRM update: resolves webhook, determines API method, calls Bitrix24 REST API, returns result
    export async function crmUpdate({ entity, entity_type_id, id, fields, params = {}, webhook_url }) {
      const client = new Bitrix24Client(resolveWebhook(webhook_url));
      const { base, extra } = resolveMethod(entity, entity_type_id);
      await client.call(`${base}.update`, { id, fields, params, ...extra });
      return { entity: entity || `SPA_${entity_type_id}`, portal: client.portal, updated_id: id, success: true };
    }
  • Helper function that maps entity name to Bitrix24 REST API method base (e.g., deal→crm.deal, SPA→crm.item with entityTypeId)
    function resolveMethod(entity, entityTypeId) {
      if (entityTypeId) return { base: 'crm.item', extra: { entityTypeId } };
      const base = ENTITY_METHOD[entity?.toLowerCase()];
      if (!base) throw new Error(`Entidad desconocida: "${entity}". Usá deal, contact, company, lead, quote, invoice, o pasá entityTypeId para SPA.`);
      return { base, extra: {} };
    }
Behavior2/5

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

With no annotations, the description carries full burden. It indicates mutation but fails to disclose partial update behavior, permission requirements, side effects, or idempotency. Minimal behavioral context.

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 single sentence is concise and to the point, with no redundant information. However, it lacks any structural formatting (e.g., sections) that might aid scanning.

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

Completeness2/5

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

For a tool with 6 parameters, no output schema, and no annotations, the description is far too brief. Missing details about return values, error handling, parameter roles, and when to use webhook_url. Incomplete for effective agent use.

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

Parameters2/5

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

Schema description coverage is only 17% (only fields has a description). The description does not explain the remaining 5 parameters (entity, entity_type_id, params, webhook_url), nor does it add meaning beyond the schema's minimal annotation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it updates fields of an existing CRM record, distinguishing it from create, delete, get, and list siblings. However, it lacks specificity about CRM entity types (e.g., leads, deals), which are hinted by the entity parameter.

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 like b24_crm_create (for new records) or b24_crm_delete. Does not mention prerequisites or conditions for updating records.

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