Skip to main content
Glama

Copy messages

copy_messages

Copy specified emails to another Outlook folder and return the IDs of the copies, so you can move messages into project or archive folders in one call.

Instructions

Copy messages to another folder; returns the IDs of the copies.

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": {
      "ids": "<ids>",
      "destination": "<destination>"
    },
    "name": "copy_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage IDs (from list_messages, search_messages or get_message)
destinationYesDestination folder. Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful fact that the copies' IDs are returned, but says nothing about partial-failure behavior, duplicate handling, permission requirements, or the 500-ID ceiling's consequences.

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 clause, front-loaded with the action and destination, followed by the return value. No wasted wording.

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?

For a simple two-parameter tool with full schema coverage and no output schema, the description supplies the one thing the schema cannot: what comes back (copy IDs). Remaining gaps around failure semantics are minor for this complexity level.

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 coverage is 100%, including source hints for 'ids' and accepted folder-name formats for 'destination', so the schema carries the parameter burden. The description adds no meaning beyond it, which is the baseline case.

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 concrete verb and resource ('Copy messages to another folder') plus the return value ('returns the IDs of the copies'). An agent can distinguish it from move_messages by the verb alone, though no sibling is named explicitly.

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 guidance on when to use copy versus move_messages, no prerequisites, and no note on what happens if a message already exists in the destination or if some IDs fail. Usage is only implied by the verb.

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