CallRail MCP

by pghdma

Overview Schema Source Related Servers Discussions Admin

Python

Remote

list_companies

List companies (client businesses) under a CallRail account.

Instructions

List companies (client businesses) under a CallRail account.

Args: account_id: CallRail account ID. Auto-resolves if omitted. per_page: Page size (max 250). status: Filter by status. Defaults to None (returns all). Common values: 'active' (excludes disabled/soft-deleted), 'disabled'. page: 1-indexed. Agencies with more than per_page companies need this to reach the rest. Previously there was no way to fetch page 2 via this tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`status`	No
`per_page`	No
`account_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.4Jul 6, 2026
- addedInput schema / properties / page
```
Added value: +{
+  "default": 1,
+  "title": "Page",
+  "type": "integer"
+}
```
First observedv1.0.0Apr 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and handles it well. It discloses default filtering behavior, pagination semantics, the 250-item limit, the meaning of 'active' (excludes disabled/soft-deleted), and the previously missing ability to fetch page 2. This is strong transparency for a list operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is compact, front-loaded with the core operation, and followed by a clear Args block. Every sentence adds value, including the brief historical note about page 2, which clarifies an important capability without padding.

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?

All optional parameters are documented with defaults and edge cases, and the output schema exists to cover return values. For a simple listing tool, the description leaves no significant operational detail missing.

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?

The input schema has 0% description coverage, leaving the parameters otherwise opaque. The Args block compensates by explaining all four parameters: account_id auto-resolution, per_page maximum, status values/defaults, and page indexing/pagination usage.

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 opening sentence states a specific verb and resource: 'List companies (client businesses) under a CallRail account.' This clearly distinguishes the tool from list_accounts, list_trackers, and other listing siblings by identifying the exact entity type and scope.

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?

The description gives clear invocation context: account_id auto-resolves, per_page has a documented max, status has defined defaults, and page is explicitly needed when an agency has more companies than per_page. It does not name alternative tools or explicit when-not-to-use cases, but provides solid situational guidance for the parameters.

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

Deploy Server