CallRail MCP

Overview Schema Source Related Servers Discussions Admin

update_company

Update mutable settings on a company. Pass None to leave a field unchanged; only fields with explicit values are sent in the PUT body.

Instructions

Update mutable settings on a company. Pass None to leave a field unchanged; only fields with explicit values are sent in the PUT body.

CRITICAL: Any boolean toggle you set will OVERRIDE current state. If a company has CallScribe enabled and you call update_company(name='New Name') without passing callscribe_enabled, CallScribe stays on. But passing callscribe_enabled=False will DISABLE CallScribe (a paid feature). Be deliberate with bool args.

Empty-string name / time_zone are rejected (almost always a mistake; pass None to leave them alone).

Args: company_id: 'COM...' id. name: New display name. Empty string rejected. Max 255 chars. time_zone: IANA tz string (e.g. 'America/New_York'). callscore_enabled: Lead-scoring AI feature. PAID add-on. lead_scoring_enabled: Older lead-scoring system. swap_exclude_jquery: Skip jQuery initialization in DNI script. callscribe_enabled: Conversation Intelligence (transcripts + keyword spotting). PAID feature. keyword_spotting_enabled: DEPRECATED by CallRail. Accepted for compatibility but has no effect. swap_exclude_jquery: DEPRECATED by CallRail (the DNI script no longer needs jQuery). Accepted but has no effect. form_capture: Enable CallRail Form Tracking on this company. Sent as CallRail's external_form_capture PUT field. account_id: CallRail account ID. Auto-resolves if omitted.

Returns: JSON string with the updated company object.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`time_zone`	No
`account_id`	No
`company_id`	Yes
`form_capture`	No
`callscore_enabled`	No
`callscribe_enabled`	No
`swap_exclude_jquery`	No
`lead_scoring_enabled`	No
`keyword_spotting_enabled`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses PUT merge behavior, boolean override risk, empty-string rejection, deprecations, field mapping, and account auto-resolution. This is unusually transparent for a mutation tool.

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 organized with a critical warning, an Args block, and a Returns line; most content earns its place. The duplicate swap_exclude_jquery entry is redundant and could be merged, and the warning section could be tightened slightly.

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

Completeness4/5

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

For a 10-parameter mutation with no annotations and no schema descriptions, the description is nearly complete: all parameters, edge cases, deprecations, and return type are addressed. The contradictory swap_exclude_jquery duplicate leaves one parameter ambiguous, and permission requirements are not stated.

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

Parameters4/5

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

Schema coverage is 0%, so the description compensates richly for every parameter with constraints, examples, paid status, deprecation notes, and field mapping. One blemish is the duplicated and internally contradictory swap_exclude_jquery entry: it is described both as 'Skip jQuery initialization' and as having no effect, which blurs that parameter's true behavior.

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?

States a precise verb and resource: 'Update mutable settings on a company.' It clearly differentiates from read-only get_company, create_company, and delete_company siblings by focusing on mutable settings.

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 usage semantics: pass None to leave fields unchanged, only explicit values are sent, and booleans override current state, with a concrete CallScribe example. It does not explicitly name alternatives or state when not to use this tool, but the context is clear enough for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server