Skip to main content
Glama

AIsa Agent Mail

by one.aisa
OverviewDiscussionsAdmin

Get Inbox Message

patch_agentmail_inbox_message
Destructive

Retrieve detailed information about a specific message within an inbox, including sender, recipients, content, labels, attachments, and timestamps.

Published reference price: $0.012 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
bodyNo
inbox_idYesThe ID of the inbox.
message_idYesID of message.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / add_labels
      Removed value: -{
-  "description": "Label or labels to add to message.",
-  "oneOf": [
-    {
-      "type": "string"
-    },
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  ],
-  "title": "UpdateMessageLabels"
-}
    • addedInput schema / properties / body
      Added value: +{
+  "properties": {
+    "add_labels": {
+      "description": "Label or labels to add to message.",
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      ],
+      "title": "UpdateMessageLabels"
+    },
+    "remove_labels": {
+      "description": "Label or labels to remove from message.",
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      ],
+      "title": "UpdateMessageLabels"
+    }
+  },
+  "title": "UpdateMessageRequest",
+  "type": "object"
+}
    • removedInput schema / properties / remove_labels
      Removed value: -{
-  "description": "Label or labels to remove from message.",
-  "oneOf": [
-    {
-      "type": "string"
-    },
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  ],
-  "title": "UpdateMessageLabels"
-}
  2. Changed4 schema fields changed
    • removedInput schema / properties / add_labels / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]
    • addedInput schema / properties / add_labels / oneOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • removedInput schema / properties / remove_labels / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]
    • addedInput schema / properties / remove_labels / oneOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
  3. Changed2 schema fields changed
    • removedInput schema / properties / Authorization
      Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id",
-  "message_id",
-  "Authorization"
-]New value: +[
+  "inbox_id",
+  "message_id"
+]
  4. Changed2 schema fields changed
    • addedInput schema / properties / Authorization
      Added value: +{
+  "description": "Bearer authentication",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id",
-  "message_id"
-]New value: +[
+  "inbox_id",
+  "message_id",
+  "Authorization"
+]
  5. Changed2 schema fields changed
    • removedInput schema / properties / Authorization
      Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id",
-  "message_id",
-  "Authorization"
-]New value: +[
+  "inbox_id",
+  "message_id"
+]
  6. First observed

TDQS

D1.3/5.0
Behavior1/5

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

The description claims a pure retrieval, while annotations declare readOnlyHint=false and destructiveHint=true and the schema exposes add_labels/remove_labels mutations. This directly contradicts both structured sources and hides the destructive label-modification behavior an agent must know about.

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?

Two sentences plus a pricing block; it is short and front-loaded, but the content is factually wrong for the tool, so the brevity is not earned. The pricing boilerplate is incidental noise.

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

Completeness1/5

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

For a destructive patch operation with an output schema and a nested body object, the description fails to explain the mutation, the label add/remove semantics, or any prerequisites. It is actively incomplete and misdirecting.

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

Parameters2/5

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

The word 'labels' in the description refers to returned fields, not the input body parameters add_labels/remove_labels, so it adds no meaning about the 3 inputs. With only 67% schema coverage, the body object's add/remove label semantics go unexplained in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says the tool will 'Retrieve detailed information about a specific message,' which is a read operation, but the tool name is patch_agentmail_inbox_message and the schema requires a body with add_labels/remove_labels. This describes the wrong operation entirely and collides with the sibling get_agentmail_inbox_message.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

No when-to-use guidance is given, and the implied guidance is misleading: an agent reading this would invoke it as a read, when the actual read tool is the sibling get_agentmail_inbox_message. No alternatives or conditions are mentioned.

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

All AIsa Agent Mail toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources