Skip to main content
Glama
pghdma

CallRail MCP

update_company

Update mutable company settings like name, time zone, and AI features. Pass null to leave a field unchanged; boolean toggles override current state.

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: Flag calls containing watch-list keywords. form_capture: Enable CallRail Form Tracking on this company. account_id: CallRail account ID. Auto-resolves if omitted.

Returns: JSON string with the updated company object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
time_zoneNo
account_idNo
company_idYes
form_captureNo
callscore_enabledNo
callscribe_enabledNo
swap_exclude_jqueryNo
lead_scoring_enabledNo
keyword_spotting_enabledNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully covers behavioral traits: PUT method implied, boolean override critical warning, empty string rejection, and account_id auto-resolution. It does not mention authentication or rate limits, but adequately covers key mutation caveats.

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 a summary sentence, critical warnings in block, then parameter list. Slightly long but front-loaded. Every sentence adds value.

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 10 parameters, no annotations, and presence of output schema, the description is complete: explains parameter behavior, critical risks, and return value. No gaps for correct invocation.

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

Parameters5/5

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

Despite 0% schema coverage, the description adds rich meaning for each parameter: explains purpose (e.g., 'callscribe_enabled: Conversation Intelligence'), notes PAID add-ons, specifies constraints (empty string rejection, max 255 chars), and clarifies the None semantics for optional fields.

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 'Update mutable settings on a company', specifying verb and resource. The description distinguishes this from sibling tools like create_company or get_company by focusing on mutations and listing settable fields.

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 guidelines: pass None to leave unchanged, be deliberate with booleans, avoid empty strings. It does not explicitly contrast with alternatives but the context makes it clear when to use this 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/pghdma/callrail-mcp'

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