Skip to main content
Glama

Artil — Email, SMS & Messaging for AI Agents

Read a message

messages.read
Read-only

Read a message the agent account received or sent, with its text and the files it came with. A sent message that failed has an error saying why. Each file has a download link that works for 15 minutes with no sign-in; read the message again for a fresh one.

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": {
      "id": "<id>"
    },
    "name": "messages.read"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe message's id, from messages.list or an event
agentNoThe id of the agent account to act as, from status. Leave it out when these tools act as one agent account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / agent / format
      Removed value: -"uuid"
    • removedInput schema / properties / agent / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, non-openWorld, so the safety profile is covered. The description adds real context beyond that: failed sent messages carry an explanatory error, and file links expire after 15 minutes and need no sign-in, requiring a re-read. It does not mention any access prerequisites, but the behavioral surface is otherwise well disclosed.

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?

Three short sentences, front-loaded with what is returned, then the failure case, then the link expiry caveat. No filler and nothing redundant.

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?

For a two-parameter read tool with no output schema, the description covers what is returned (text, files), the error case for failed sends, and the operationally important 15-minute link expiry with the remedy. An agent has everything needed to call it and interpret the result.

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 description coverage is 100%, so both the id and agent parameters are already documented, including where to get the id and when to omit agent. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("Read a message") plus the scope (received or sent by the agent account) and what comes back (text and attached files). That distinguishes it implicitly from messages.list, since this is a single-message retrieval, but the sibling is never named.

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 rather than stated: read one message by id from messages.list or an event. It does give a useful operational cue — read the message again to get a fresh download link — but there is no explicit when-to-use vs when-not guidance relative to messages.list or messages.send.

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