Skip to main content
Glama

insync_list_messages

Read-only

List secure portal messages by folder (unread, read, sent) with search and attachment filters. Returns sender, subject, date, attachment count, and IDs to open full messages without marking read.

Instructions

List secure messages from your practice — unread, read or sent. Returns sender, recipient, subject, date, attachment count and the ids insync_get_message needs. Listing does NOT mark anything read.

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": "insync_list_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Default 1.
viewNocompact (default) projects each record to the fields a caller acts on; "full" keeps every field this server understands; "brief" returns one line per message: <subject> (from <sender>) — <ISO date> — <folder>. (No "raw": the record is assembled here.)
folderNoWhich folder to list. Default unread.unread
searchNoFilter to messages matching this text.
archivedNoWhen true, list archived messages.
page_sizeNoMessages per page (1–100). Default 25.
has_attachmentNoWhen true, list only messages that carry an attachment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact projects each record to the fields a caller acts on; \"full\" keeps every field this server understands. (No \"raw\": the record is assembled here, not passed through from one endpoint.)"New value: +"compact (default) projects each record to the fields a caller acts on; \"full\" keeps every field this server understands; \"brief\" returns one line per message: <subject> (from <sender>) — <ISO date> — <folder>. (No \"raw\": the record is assembled here.)"
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "compact",
      -  "full"
      -]New value: +[
      +  "compact",
      +  "full",
      +  "brief"
      +]
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but they cannot express the specific side-effect guarantee the description makes: "Listing does NOT mark anything read." That is exactly the reassurance an agent needs before listing an unread inbox, and the enumerated return fields add further behavioral context. It stops short of 5 because pagination/total-count behavior and ordering are not described.

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?

Two sentences, zero filler, and the scope constraint is front-loaded before the return-value list and the side-effect caveat. Every clause earns its place.

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?

With seven optional parameters, no output schema, and full schema coverage, the description supplies the missing pieces: what fields come back and what the ids are for. Ordering, pagination cursors and total counts are left unstated, which is a minor gap for a listing tool but not one that would cause a mis-call.

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 folder enums, page/page_size bounds, search, archived and has_attachment are all already documented in the schema. The description echoes the folder values ("unread, read or sent") but adds no syntax, matching semantics, or interaction rules (e.g. how archived combines with folder). Baseline 3 applies when the schema carries the parameter detail.

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 secure messages from your practice") plus the scope covered ("unread, read or sent"), and enumerates what comes back. It also implicitly distinguishes itself from the single-message sibling by referencing "the ids insync_get_message needs", so an agent can tell list from fetch without opening either schema.

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

Usage Guidelines4/5

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

Gives clear context for use: pick a folder, optionally filter, and take the returned ids to insync_get_message. There is no explicit when-not-to-use statement (e.g. use insync_get_counts for totals, or insync_list_attachments for attachment-centric browsing), so it stops short of full routing guidance.

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