Skip to main content
Glama

imap_copy_message

Copies a message to a specified mailbox, supporting same-account or cross-account transfers when a destination account is provided.

Instructions

Copy a message to mailbox

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": {
      "message_id": "<message_id>",
      "destination_mailbox": "<destination_mailbox>"
    },
    "name": "imap_copy_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoAccount identifier (defaults to `"default"`)default
message_idYesStable message identifier
destination_mailboxYesDestination mailbox name
destination_account_idNoDestination account (if omitted, copies within same account)

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds nothing beyond that: it does not state that the original message is retained, that repeated calls create duplicates (non-idempotent), or that cross-account copies are possible even though the schema supports destination_account_id.

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

Conciseness3/5

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

It is a single six-word sentence with no waste, and the verb is front-loaded. However, the terseness crosses into under-specification, so there is no structure beyond a bare purpose fragment.

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 structured data is rich here: full parameter descriptions and an output schema mean return values and argument meaning need not be repeated. What is still missing is behavioral context an agent would want for a non-idempotent mutating copy operation, notably copy-vs-move routing and duplicate-copy behavior.

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 every parameter (account_id, message_id, destination_mailbox, destination_account_id) is already documented in the input schema, including the same-account vs cross-account semantics. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 gives a specific verb and resource ("Copy a message") plus a destination ("to mailbox"), so an agent can tell what the tool does. It stops short of distinguishing copy from the sibling imap_move_message, leaving the copy-vs-move distinction to inference from the tool name alone.

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?

There is no when-to-use guidance, no mention of the move alternative, and no prerequisites such as the destination mailbox needing to exist or the source message needing to remain in place. Usage is only implied by the verb "Copy".

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