Skip to main content
Glama

AIsa Agent Mail

by one.aisa
OverviewDiscussionsAdmin

Manage Inbox

patch_agentmail_inbox
Destructive

Retrieve, update, or delete a specific inbox by its ID. Returns inbox details including email, display name, client ID, 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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / body
      Added value: +{
+  "properties": {
+    "display_name": {
+      "description": "Display name: `Display Name <username@domain.com>`.",
+      "title": "DisplayName",
+      "type": "string"
+    },
+    "metadata": {
+      "description": "Metadata to merge into the inbox's existing metadata. Keys you include\nare added or overwritten; keys you omit are left unchanged. To remove a\nsingle key, send it with a null value. To clear all metadata, send\n`metadata` as null. Sending an empty object is rejected; use null to\nclear. Each update must include at least one of `display_name`,\n`status`, or `metadata`.",
+      "oneOf": [
+        {
+          "additionalProperties": {
+            "oneOf": [
+              {
+                "description": "A metadata value. May be a string, number, or boolean.",
+                "oneOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "format": "double",
+                    "type": "number"
+                  },
+                  {
+                    "type": "boolean"
+                  }
+                ],
+                "title": "MetadataValue"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
+          "title": "UpdateMetadata",
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "description": "`paused` stops the inbox sending and receiving mail; `active` resumes\nit. Mail that arrived while the inbox was paused is not delivered on\nresume.",
+      "enum": [
+        "active",
+        "paused"
+      ],
+      "title": "InboxStatus",
+      "type": "string"
+    }
+  },
+  "title": "UpdateInboxRequest",
+  "type": "object"
+}
    • removedInput schema / properties / display_name
      Removed value: -{
-  "description": "Display name: `Display Name <username@domain.com>`.",
-  "title": "DisplayName",
-  "type": "string"
-}
    • removedInput schema / properties / metadata
      Removed value: -{
-  "description": "Metadata to merge into the inbox's existing metadata. Keys you include\nare added or overwritten; keys you omit are left unchanged. To remove a\nsingle key, send it with a null value. To clear all metadata, send\n`metadata` as null. Sending an empty object is rejected; use null to\nclear. Each update must include at least one of `display_name`,\n`status`, or `metadata`.",
-  "oneOf": [
-    {
-      "additionalProperties": {
-        "oneOf": [
-          {
-            "description": "A metadata value. May be a string, number, or boolean.",
-            "oneOf": [
-              {
-                "type": "string"
-              },
-              {
-                "format": "double",
-                "type": "number"
-              },
-              {
-                "type": "boolean"
-              }
-            ],
-            "title": "MetadataValue"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
-      "title": "UpdateMetadata",
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • removedInput schema / properties / status
      Removed value: -{
-  "description": "`paused` stops the inbox sending and receiving mail; `active` resumes\nit. Mail that arrived while the inbox was paused is not delivered on\nresume.",
-  "enum": [
-    "active",
-    "paused"
-  ],
-  "title": "InboxStatus",
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • removedInput schema / properties / metadata / anyOf
      Removed value: -[
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "format": "double",
-              "type": "number"
-            },
-            {
-              "type": "boolean"
-            }
-          ],
-          "description": "A metadata value. May be a string, number, or boolean.",
-          "title": "MetadataValue"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
-    "title": "UpdateMetadata",
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / metadata / oneOf
      Added value: +[
+  {
+    "additionalProperties": {
+      "oneOf": [
+        {
+          "description": "A metadata value. May be a string, number, or boolean.",
+          "oneOf": [
+            {
+              "type": "string"
+            },
+            {
+              "format": "double",
+              "type": "number"
+            },
+            {
+              "type": "boolean"
+            }
+          ],
+          "title": "MetadataValue"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
+    "title": "UpdateMetadata",
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Changed5 schema fields changed
    • removedInput schema / properties / Authorization
      Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}
    • changedInput schema / properties / metadata / anyOf
      Previous value: -[
-  {
-    "allOf": [
-      {
-        "additionalProperties": {
-          "anyOf": [
-            {
-              "allOf": [
-                {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "format": "double",
-                      "type": "number"
-                    },
-                    {
-                      "type": "boolean"
-                    }
-                  ],
-                  "description": "A metadata value. May be a string, number, or boolean.",
-                  "title": "MetadataValue"
-                }
-              ]
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
-        "title": "UpdateMetadata",
-        "type": "object"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "format": "double",
+              "type": "number"
+            },
+            {
+              "type": "boolean"
+            }
+          ],
+          "description": "A metadata value. May be a string, number, or boolean.",
+          "title": "MetadataValue"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
+    "title": "UpdateMetadata",
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / metadata / description
      Previous value: -"Metadata to merge into the inbox's existing metadata. Keys you include\nare added or overwritten; keys you omit are left unchanged. To remove a\nsingle key, send it with a null value. To clear all metadata, send\n`metadata` as null. Sending an empty object is rejected; use null to\nclear. Each update must include at least one of `display_name` or\n`metadata`."New value: +"Metadata to merge into the inbox's existing metadata. Keys you include\nare added or overwritten; keys you omit are left unchanged. To remove a\nsingle key, send it with a null value. To clear all metadata, send\n`metadata` as null. Sending an empty object is rejected; use null to\nclear. Each update must include at least one of `display_name`,\n`status`, or `metadata`."
    • addedInput schema / properties / status
      Added value: +{
+  "description": "`paused` stops the inbox sending and receiving mail; `active` resumes\nit. Mail that arrived while the inbox was paused is not delivered on\nresume.",
+  "enum": [
+    "active",
+    "paused"
+  ],
+  "title": "InboxStatus",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id",
-  "Authorization"
-]New value: +[
+  "inbox_id"
+]
  4. Changed5 schema fields changed
    • addedInput schema / properties / Authorization
      Added value: +{
+  "description": "Bearer authentication",
+  "type": "string"
+}
    • changedInput schema / properties / metadata / anyOf
      Previous value: -[
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "format": "double",
-              "type": "number"
-            },
-            {
-              "type": "boolean"
-            }
-          ],
-          "description": "A metadata value. May be a string, number, or boolean.",
-          "title": "MetadataValue"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
-    "title": "UpdateMetadata",
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "allOf": [
+      {
+        "additionalProperties": {
+          "anyOf": [
+            {
+              "allOf": [
+                {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "format": "double",
+                      "type": "number"
+                    },
+                    {
+                      "type": "boolean"
+                    }
+                  ],
+                  "description": "A metadata value. May be a string, number, or boolean.",
+                  "title": "MetadataValue"
+                }
+              ]
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
+        "title": "UpdateMetadata",
+        "type": "object"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / metadata / description
      Previous value: -"Metadata to merge into the inbox's existing metadata. Keys you include\nare added or overwritten; keys you omit are left unchanged. To remove a\nsingle key, send it with a null value. To clear all metadata, send\n`metadata` as null. Sending an empty object is rejected; use null to\nclear. Each update must include at least one of `display_name`,\n`status`, or `metadata`."New value: +"Metadata to merge into the inbox's existing metadata. Keys you include\nare added or overwritten; keys you omit are left unchanged. To remove a\nsingle key, send it with a null value. To clear all metadata, send\n`metadata` as null. Sending an empty object is rejected; use null to\nclear. Each update must include at least one of `display_name` or\n`metadata`."
    • removedInput schema / properties / status
      Removed value: -{
-  "description": "`paused` stops the inbox sending and receiving mail; `active` resumes\nit. Mail that arrived while the inbox was paused is not delivered on\nresume.",
-  "enum": [
-    "active",
-    "paused"
-  ],
-  "title": "InboxStatus",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id"
-]New value: +[
+  "inbox_id",
+  "Authorization"
+]
  5. Changed5 schema fields changed
    • removedInput schema / properties / Authorization
      Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}
    • changedInput schema / properties / metadata / anyOf
      Previous value: -[
-  {
-    "allOf": [
-      {
-        "additionalProperties": {
-          "anyOf": [
-            {
-              "allOf": [
-                {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "format": "double",
-                      "type": "number"
-                    },
-                    {
-                      "type": "boolean"
-                    }
-                  ],
-                  "description": "A metadata value. May be a string, number, or boolean.",
-                  "title": "MetadataValue"
-                }
-              ]
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
-        "title": "UpdateMetadata",
-        "type": "object"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "format": "double",
+              "type": "number"
+            },
+            {
+              "type": "boolean"
+            }
+          ],
+          "description": "A metadata value. May be a string, number, or boolean.",
+          "title": "MetadataValue"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "description": "Custom key-value pairs to merge into the inbox's existing metadata. A\nvalue may be a string, number, boolean, or null. Setting a key to null\nremoves it. Up to 256 keys; keys and string values are each limited to\n256 characters.",
+    "title": "UpdateMetadata",
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / metadata / description
      Previous value: -"Metadata to merge into the inbox's existing metadata. Keys you include\nare added or overwritten; keys you omit are left unchanged. To remove a\nsingle key, send it with a null value. To clear all metadata, send\n`metadata` as null. Sending an empty object is rejected; use null to\nclear. Each update must include at least one of `display_name` or\n`metadata`."New value: +"Metadata to merge into the inbox's existing metadata. Keys you include\nare added or overwritten; keys you omit are left unchanged. To remove a\nsingle key, send it with a null value. To clear all metadata, send\n`metadata` as null. Sending an empty object is rejected; use null to\nclear. Each update must include at least one of `display_name`,\n`status`, or `metadata`."
    • addedInput schema / properties / status
      Added value: +{
+  "description": "`paused` stops the inbox sending and receiving mail; `active` resumes\nit. Mail that arrived while the inbox was paused is not delivered on\nresume.",
+  "enum": [
+    "active",
+    "paused"
+  ],
+  "title": "InboxStatus",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id",
-  "Authorization"
-]New value: +[
+  "inbox_id"
+]
  6. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds no real behavioral context: it doesn't say this is a partial update, that at least one of display_name/status/metadata must be supplied, or how metadata merges/clears. Its return-value sentence duplicates the output schema.

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?

The two operative sentences are front-loaded and short, but they are inaccurate, and the appended aisa-pricing block is boilerplate that adds no selection value. Structure is acceptable; content efficiency is not.

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

Completeness2/5

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

An output schema exists so return values needn't be described, yet the description omits the critical update constraint (at least one updatable field required) and the boundary against the sibling get/delete tools. For a destructive, non-idempotent mutation on a nested schema, this leaves meaningful gaps.

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?

With only 50% schema description coverage and a nested body object, the description should compensate, but it says nothing about the body fields (status, metadata, display_name) or their merge semantics. 'By its ID' merely restates the required inbox_id already documented in the schema.

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

Purpose2/5

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

The description claims the tool will 'Retrieve, update, or delete a specific inbox by its ID,' but the tool name (patch_agentmail_inbox) and the dedicated siblings get_agentmail_inbox and delete_agentmail_inbox show it only performs the update. The over-broad claim actively misroutes an agent looking to read or delete an inbox.

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 when-to-use guidance is given, and the description never points to get_agentmail_inbox or delete_agentmail_inbox for the read/delete cases it erroneously claims. The only implicit guidance is the mention of an inbox ID, which the schema already requires.

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