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

get_thread

Retrieve full details of a specific email conversation thread by providing its thread ID, enabling agents to inspect message history and context.

Instructions

Get details of one conversation thread.

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

Input Schema

NameRequiredDescriptionDefault
threadIdYesThread ID from list_threads

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not disclose what 'details' includes, whether the response contains message content or metadata, or any potential limitations.

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?

A single, front-loaded sentence with no filler. It uses a clear verb and object and earns its place without unnecessary elaboration.

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?

Adequate for a simple one-parameter getter: the agent knows the resource and the required input. However, with no output schema and no annotations, 'details' is vague, and the description does not clarify what the returned thread details include or how to interpret them.

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 input schema already explains threadId and its source ('Thread ID from list_threads'). The tool description adds no additional parameter-level meaning beyond what the schema provides.

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: 'Get details of one conversation thread.' The phrase 'one conversation thread' clearly separates it from siblings like get_message (message-level) and list_threads (list-level), so an agent can distinguish it 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 Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as get_message or list_thread_messages. The only contextual hint is in the schema, where threadId is described as coming from list_threads, but the description itself provides no usage direction.

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