Skip to main content
Glama

One line's recent calls

get_line_calls
Read-onlyIdempotent

Read recent incoming call history for a prepaid line you own, newest first. Use line_id from get_answering_line. Returns items and next_before; pass that cursor as before to page within retained recent history. Answered calls include duration and summary when available. Attempts made while paused contain only id, at, caller and status paused, without audio or a transcript. Use get_line_call_transcript for an answered call. Needs lines:manage; read only and rate limited per account.

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": {
      "line_id": "<line_id>"
    },
    "name": "get_line_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25, max 100.
beforeNoISO timestamp cursor: only calls before this.
line_idYesFrom get_answering_line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already supply readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: the lines:manage scope requirement, per-account rate limiting, and the fact that attempts made while paused return only id/at/caller/status with no audio or transcript. That paused-attempt caveat is the kind of non-obvious payload limitation annotations cannot express.

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 with purpose and ordering, then pagination, payload shape, sibling hand-off, and auth constraints, with no filler sentences. It is dense and slightly packed into a single run of clauses, which costs a perfect score, but every sentence carries 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 takes on the job of describing returns (items plus next_before, duration and summary on answered calls, stripped-down paused attempts) and does so. Combined with auth and rate-limit notes, an agent has everything needed to call and page this tool correctly.

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?

Schema coverage is 100% so the baseline is 3, but the description goes further by explaining the pagination contract as a flow: the response's next_before is fed back into before, and results are limited to retained recent history. It also ties line_id to its source tool, adding provenance the schema's 'From get_answering_line' only hints at.

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 ('Read recent incoming call history'), plus scope ('for a prepaid line you own') and ordering ('newest first'). The sibling get_line_call_transcript is clearly differentiated by the instruction to use it for answered-call audio, so an agent can pick between the two without opening schemas.

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?

Explicitly routes the agent: use line_id from get_answering_line, use get_line_call_transcript for an answered call, and use next_before as the before cursor to page. It also gives the precondition (a line you own) and the paused-line edge case, so the when-to-use picture is essentially complete.

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.