Skip to main content
Glama
kojott

mailmcp

by kojott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Modify message

modify_message
DestructiveIdempotent

Mark emails read/unread, star/unstar, add/remove labels, move to folder or archive, and update UID after move.

Instructions

Mark read/unread, star/unstar, add/remove labels (Gmail labels, Outlook categories), move to a folder or archive. A move can change the id of the message: when the result carries moved_uid, use that id from then on.

Input Schema

NameRequiredDescriptionDefault
uidYesuid from search_messages
seenNo
folderNoDefault: Gmail All Mail, else INBOX
accountYeslist_accounts id
archiveNoRemove from inbox (Gmail) or move to Archive
flaggedNo
move_toNoDestination folder path
add_labelsNoGmail only
create_folderNoWith move_to: create the folder first if it does not exist
remove_labelsNoGmail only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.13.12
    • changedInput schema / properties / account / description
      Previous value: -"Account id from list_accounts"New value: +"list_accounts id"
    • addedInput schema / properties / create_folder
      Added value: +{
+  "description": "With move_to: create the folder first if it does not exist",
+  "type": "boolean"
+}
    • changedInput schema / properties / folder / description
      Previous value: -"Folder/label path. Defaults to All Mail on Gmail, INBOX elsewhere."New value: +"Default: Gmail All Mail, else INBOX"
    • changedInput schema / properties / uid / description
      Previous value: -"uid from search_messages: a number on IMAP mailboxes, an id string on Outlook; pass it back exactly as returned"New value: +"uid from search_messages"
  2. Changed6 schema fields changedv0.8.1
    • addedInput schema / properties / uid / description
      Added value: +"uid from search_messages: a number on IMAP mailboxes, an id string on Outlook; pass it back exactly as returned"
    • addedInput schema / properties / uid / maxLength
      Added value: +512
    • removedInput schema / properties / uid / maximum
      Removed value: -9007199254740991
    • addedInput schema / properties / uid / minLength
      Added value: +1
    • removedInput schema / properties / uid / minimum
      Removed value: -1
    • changedInput schema / properties / uid / type
      Previous value: -"integer"New value: +"string"
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral trait beyond the annotations: a move can change the message id, and the moved_uid in the result must be used thereafter. It still omits permission/auth requirements and what happens when a label or folder does not exist.

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 padding. The operation list is front-loaded and the id-change caveat follows immediately, which is exactly the ordering an agent needs.

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 10-parameter destructive mutation with no output schema, the description covers the main operation set plus the critical id-stability gotcha. Remaining gaps (create_folder interaction, failure behavior, permissions) are partly handled by the schema descriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so most parameters are self-documenting. The description nonetheless adds cross-provider semantics the schema lacks (Gmail labels vs Outlook categories) and clarifies the relationship between moving, archiving and folder defaults. It does not resolve the schema's 'Gmail only' wording for add_labels/remove_labels, which the Outlook mention partially contradicts.

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 names the resource (message) and enumerates the concrete operations: mark read/unread, star/unstar, add/remove labels, move/archive. An agent can tell this is the message-mutation tool. It does not, however, distinguish itself from the sibling trash_message, so the delete-vs-move boundary is left to inference.

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 enumerated operations imply when the tool applies, but there is no explicit when-to-use guidance, no prerequisites, and no named alternative (e.g., trash_message for deletion, or bulk_apply for multi-message changes). Usage is inferable from the verb list rather than stated.

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