Skip to main content
Glama

One line's recent messages

get_line_messages
Read-onlyIdempotent

List the messages the answering line took from callers for one of the signed-in owner's own lines, newest first. Each item has id, at (ISO), name, phone, message and urgent, so it holds callers' names and phone numbers. Pass the line_id from get_answering_line; limit sets the page size, and to read further back pass the previous result's next_before as before (next_before is null when there is nothing older). It reaches back through at most the 500 most recent messages. The calls themselves, with duration and summary, are in get_line_calls. Needs lines:manage; changes nothing; 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_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25, max 100.
beforeNoISO timestamp cursor: only messages 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 cover read-only, idempotent, non-destructive, and closed-world behavior, and the description adds important operational context: lines:manage permission, no changes, per-account rate limiting, and a 500-message lookback limit. It also explains pagination termination via next_before being null.

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

Conciseness5/5

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

Front-loads the purpose and scope, then moves through returned fields, pagination, related sibling, permissions, safety, and rate limits. The paragraph is dense but every sentence contributes useful 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 lists returned item fields and clarifies pagination, permissions, rate limits, and lookback constraints. It gives an agent everything needed to call and interpret this tool correctly.

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 100%, so defaults and bounds are already documented, but the description adds meaningful workflow semantics: line_id must come from get_answering_line, limit is page size, and before should be the previous result's next_before. It does not restate the schema's default/max for limit, but the cursor chaining guidance is valuable.

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 the messages') for one of the signed-in owner's own lines, newest first. It explicitly distinguishes message retrieval from call retrieval by pointing to get_line_calls.

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?

Explains that line_id comes from get_answering_line, how to paginate with limit and before/next_before, and directs the agent to get_line_calls for actual calls with duration and summary. This gives clear when-to-use and alternative guidance.

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.