Skip to main content
Glama

List call history

list_calls
Read-only

List compact call history for the signed-in user, without transcripts or call instructions. Use a returned id with get_call_transcript to read the conversation before judging the user's goal. direction=inbound requires Unlimited Reserve Plus and an active reserved number, or a number on the user's own Twilio account connected to ClawCall.

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_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return, 1–200. Default 25.
sinceNoISO-8601 timestamp. Filters by when the call finalized, not when it started. Overlap windows when polling inbound.
directionNooutbound or inbound. Omit for both.

Output Schema

NameRequiredDescriptionDefault
callsYes
recordingWindowMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: rows are compact (no transcripts/instructions) and inbound filtering depends on Unlimited Reserve Plus plus an active reserved number or a ClawCall-connected Twilio number. It does not discuss pagination or ordering of results.

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?

Three sentences, front-loaded with purpose and the transcript caveat, then prerequisites. Every sentence carries information, though the final prerequisite sentence is dense and could be split for faster scanning.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. Purpose, content scope, routing to get_call_transcript and inbound entitlement requirements are all present; only minor operational details like result ordering are unaddressed.

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%, so limit, since and direction are already fully documented with defaults, bounds and the finalization-time semantics. The description only adds the entitlement constraint on direction=inbound, which is useful but is not per-parameter syntax the schema lacks — baseline 3 applies.

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 ("List compact call history") plus the signed-in user scope, and explicitly narrows content by excluding transcripts and call instructions. That exclusion cleanly separates it from get_call_transcript, which the sibling list confirms exists.

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

Usage Guidelines5/5

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

Gives explicit routing guidance: use a returned id with get_call_transcript to read the conversation before judging the user's goal. It also states the account prerequisites that must hold for direction=inbound, so the agent knows when the filter will fail rather than guessing.

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.