Skip to main content
Glama
Sign In
EngageLab Agent Email MCP Server

EngageLab Agent Email MCP Server

Official
by Metaverse-Cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_thread_messages

Retrieve all email messages in a conversation thread, ordered from oldest to newest, to review the complete email history.

Instructions

List all messages inside a conversation thread, oldest first.

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": {
      "threadId": "<threadId>"
    },
    "name": "list_thread_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number, starts at 1
pageSizeNoPage size
threadIdYesThread ID from list_threads

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral burden. It discloses the 'oldest first' ordering and that it lists all messages, which are useful behavioral details, but it omits pagination behavior, error cases, and any side-effect or auth implications.

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?

The description is a single, front-loaded sentence. It conveys the action, scope, and ordering with no filler, and every word contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and its parameters are well documented, but with no annotations and no output schema, the description leaves some gaps: pagination defaults, response shape, and how it differs from get_thread are not clarified. It is adequate but not fully self-sufficient.

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 the schema already documents threadId, pageNo, and pageSize well, including the note that threadId comes from list_threads. The description adds little beyond what the schema already provides, so the baseline 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?

The description states a specific action and resource: 'List all messages inside a conversation thread, oldest first.' It clearly conveys the scope and order, though it does not explicitly distinguish itself from the sibling get_thread tool.

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?

The intended use is implied: call this when you need the messages within a thread. However, it does not explicitly identify when to choose this over related tools like get_thread or list_threads, nor does it state any exclusions.

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

Deploy Server

Other Tools