CorpusIQ

Callrail Connector

callrail_connector

Read-onlyIdempotent

CallRail call-tracking read access via the CorpusIQ breadth tier (sourced through Nango, not a first-party connector). Read-only: list accounts, companies, tracking numbers, and calls (with source, duration, and caller data). Call-attribution, phone-lead, and which-campaign-drove-calls questions. Writes are not exposed (default-deny). When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes	callrail_list_accounts: List the CallRail accounts this connection can access. Returns each account's id and name. Call this first to resolve th \| callrail_get_account: Get a single CallRail account summary by account_id (name, id, features). Requires account_id from callrail_list_account \| callrail_list_companies: List the companies (tracked businesses) under a CallRail account. Requires account_id. [Breadth-tier connector via Nango \| callrail_list_calls: List calls tracked under a CallRail account: tracking number, duration, start time, source, and caller data. Requires ac \| callrail_list_trackers: List the tracking numbers (trackers) configured under a CallRail account. Requires account_id. [Breadth-tier connector v
`params`	No	Action-specific parameters. callrail_list_accounts: none \| callrail_get_account: {account_id: string} \| callrail_list_companies: {account_id: string} \| callrail_list_calls: {account_id: string} \| callrail_list_trackers: {account_id: string}

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world. The description reinforces read-only and adds substantial context: default-deny on writes, a provenance token flow (15-minute window, any replica, source_path mapping), chart_render labeling semantics, attribution footer handling, and a data accuracy contract. This goes well beyond annotations.

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

Conciseness2/5

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

The description is lengthy and front-loaded correctly, but it haws into multiple tangential domains (provenance tokens, chart_render routing, footer verbatim requirements, data accuracy contract). Many of these are operational policies that dilute the core tool purpose and would be better placed in separate documentation or a shared policy tool.

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 read-only connector with no output schema, the description is quite complete: it enumerates resource types, return fields, safety posture, and integration with chart_render. The provenance and footer instructions are detailed, though they may be overkill for a connector tool. The completeness is strong, but the description lacks explicit error-handling or pagination behavior for calls.

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

Parameters3/5

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

Schema coverage is 100% and the enum descriptions are detailed (each action includes required params and return summary). The description lists the same resources but adds no new parameter-level detail beyond what the schema and nested enum descriptions already provide. Baseline 3 is appropriate.

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 specific verb+resource (read access to CallRail call-tracking), names the exact data returned (accounts, companies, tracking numbers, calls with source/duration/caller), and distinguishes from first-party connectors by noting it's a breadth-tier connector via Nango.

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?

Clearly routes use cases (call-attribution, phone-lead, which-campaign-drove-calls questions) and explicitly states writes are not exposed (default-deny). Also directs to chart_render for visuals. However, it does not contrast with sibling connectors like google_ads_connector or clarify when to use this vs. another CRM connector.

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

All CorpusIQ tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?