Skip to main content
Glama

List call history

list_call_history
Read-onlyIdempotent

The account's calls, newest first, from the phone system, AI agents, the account's own voice workspace and WhatsApp calling, one row shape: when, direction, numbers (last four digits), extension and its user, contact, AI agent or person, campaign, outcome, duration, closing sentiment, test flag. Filter by handled_by, outcome, direction, extension (digits) and campaign_id (ids as list_voice_campaigns returns them, or "none" for no campaign), and by an AI objective's result (evaluation_id with evaluation_result, always both; phone-system rows are left out then). Covers the last 30 days unless since is given; page with meta.next_cursor. meta.warming, meta.phone_unavailable or meta.incomplete true means the list is incomplete. Campaign (campaign_id), sentiment and AI agent (handled_by, ai_agent) data apply only when the account has that feature (contact center, AI decisions, AI phone agents or a connected voice workspace); without it rows omit those fields and those filters are ignored, so an absent field does not mean no campaign or a person.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_call_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO 8601 date or time; calls from then on.
untilNoISO 8601 date or time; calls up to then.
cursorNometa.next_cursor of the previous answer.
fieldsNoOptional: return only these fields of each record.
outcomeNo
per_pageNoDefaults to 25.
directionNo
extensionNo
handled_byNoIgnored without the AI phone agents or voice workspace feature.
campaign_idNoIds from list_voice_campaigns; "none": no campaign. Ignored without contact center.
evaluation_idNoAn objective (criterion in get_ai_call_report quality.evaluations).
evaluation_resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / handled_by / description
      Previous value: -"Ignored without the AI phone agents feature."New value: +"Ignored without the AI phone agents or voice workspace feature."
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent safety, and the description adds substantial behavior the agent could not otherwise know: ordering, the 30-day default window, silent ignoring of filters when the account lacks a feature, and the meaning of meta.warming/phone_unavailable/incomplete. The warning that an absent field does not mean 'no campaign' or 'no person' is exactly the kind of trap an agent needs disclosed.

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?

Purpose and ordering are front-loaded, then return shape, then filters, then caveats — a sensible sequence. The prose is dense and runs long in single sentences, which makes it harder to scan, but nearly every clause carries distinct information.

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?

With no output schema, the description carries the full burden and discharges it: row fields, meta cursor, the incompleteness flags, and the conditional presence of campaign/sentiment/AI-agent data are all described. Feature-gating and silent-filter behavior are covered, so an agent can call it correctly without guessing.

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 67%, and the description compensates by explaining filter semantics beyond the schema: extension must be digits, campaign_id accepts ids or "none", evaluation_id/evaluation_result must always be used together, and feature-gated filters (handled_by, campaign_id) are silently ignored. It leaves until, per_page and fields entirely to the schema, which does document them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb+resource ('The account's calls, newest first') and immediately scopes the sources (phone system, AI agents, voice workspace, WhatsApp calling) plus the returned row shape. It does not distinguish itself from siblings like get_call or conversation_list, so it stops short of a 5.

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?

It provides real operational guidance: default 30-day window unless 'since' is given, cursor pagination via meta.next_cursor, and the rule that evaluation_id must be paired with evaluation_result. However, it never states when to prefer this over get_call or the conversation list tools, so the when-to-use vs alternatives is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources