Skip to main content
Glama
CallRail MCP

CallRail MCP

by pghdma

search_calls_by_number

Read-onlyIdempotent

Find all calls to or from a specific phone number in CallRail. Matches the last 10 digits, so any format works, and supports a lookback window plus optional company filtering.

Instructions

Find calls from/to a specific phone number. Matches on the last 10 digits of the stored customer_phone_number so any format works.

Args: phone_number: Any format, normalized to digits-only. Must contain at least 7 digits to avoid false positives. account_id: Auto-resolves. company_id: Optional company filter. days: Lookback window (default 90).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "phone_number": "<phone_number>"
    },
    "name": "search_calls_by_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
account_idNo
company_idNo
phone_numberYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.2
    • addedInput schema / properties / phone_number / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "integer"
      +  }
      +]
    • removedInput schema / properties / phone_number / type
      Removed value: -"string"
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavior: the last-10-digit normalization, the 7-digit minimum to avoid false positives, auto-resolution of account_id, and a 90-day default lookback. It does not discuss result caps or pagination, which would have completed the picture.

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?

Front-loaded purpose sentence followed by a compact per-argument list; each line adds information rather than restating the schema titles. Slightly terse but no wasted text.

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?

With annotations covering safety and an output schema covering return shape, the description supplies the match semantics, argument behavior, and defaults an agent needs to invoke it correctly. Only pagination/result-limit expectations are unaddressed.

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 must carry all parameter meaning, and it largely does: phone_number accepts any format and is normalized to digits with a 7-digit floor, account_id auto-resolves, company_id is an optional company filter, and days defaults to 90. Only 'auto-resolves' for account_id stays slightly vague about what the agent must supply.

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 and resource plus the matching rule: 'Find calls from/to a specific phone number', matched on the last 10 digits of customer_phone_number. That matching rule alone makes it unmistakable next to generic listing tools like list_calls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phone-number focus and the days lookback window, but there is no explicit when-to-use/when-not-to-use guidance and no sibling (e.g. list_calls) is named as the alternative for non-phone-based filters.

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