Skip to main content
Glama

AIsa Agent Mail

by one.aisa
OverviewDiscussionsAdmin

List And Create Inboxes

post_agentmail_inbox
Destructive

Retrieve a list of inboxes with pagination support or create a new inbox with optional custom username, domain, and display name.

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

Input Schema

NameRequiredDescriptionDefault
bodyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / body
      Added value: +{
+  "properties": {
+    "client_id": {
+      "description": "Client ID of inbox.",
+      "title": "ClientId",
+      "type": "string"
+    },
+    "display_name": {
+      "description": "Display name: `Display Name <username@domain.com>`.",
+      "title": "DisplayName",
+      "type": "string"
+    },
+    "domain": {
+      "description": "Domain of address. Must be a verified domain, or any subdomain of a\nverified domain that has subdomains enabled (e.g., `bot.example.com`).\nDefaults to `agentmail.to`.",
+      "type": "string"
+    },
+    "metadata": {
+      "additionalProperties": {
+        "description": "A metadata value. May be a string, number, or boolean.",
+        "oneOf": [
+          {
+            "type": "string"
+          },
+          {
+            "format": "double",
+            "type": "number"
+          },
+          {
+            "type": "boolean"
+          }
+        ],
+        "title": "MetadataValue"
+      },
+      "description": "Custom metadata to attach to the inbox.",
+      "title": "Metadata",
+      "type": "object"
+    },
+    "status": {
+      "description": "Set `paused` to create the inbox paused.",
+      "enum": [
+        "active",
+        "paused"
+      ],
+      "title": "InboxStatus",
+      "type": "string"
+    },
+    "username": {
+      "description": "Username of address. Randomly generated if not specified.",
+      "type": "string"
+    }
+  },
+  "title": "CreateInboxRequest",
+  "type": "object"
+}
    • removedInput schema / properties / client_id
      Removed value: -{
-  "description": "Client ID of inbox.",
-  "title": "ClientId",
-  "type": "string"
-}
    • removedInput schema / properties / display_name
      Removed value: -{
-  "description": "Display name: `Display Name <username@domain.com>`.",
-  "title": "DisplayName",
-  "type": "string"
-}
    • removedInput schema / properties / domain
      Removed value: -{
-  "description": "Domain of address. Must be a verified domain, or any subdomain of a\nverified domain that has subdomains enabled (e.g., `bot.example.com`).\nDefaults to `agentmail.to`.",
-  "type": "string"
-}
    • removedInput schema / properties / metadata
      Removed value: -{
-  "additionalProperties": {
-    "description": "A metadata value. May be a string, number, or boolean.",
-    "oneOf": [
-      {
-        "type": "string"
-      },
-      {
-        "format": "double",
-        "type": "number"
-      },
-      {
-        "type": "boolean"
-      }
-    ],
-    "title": "MetadataValue"
-  },
-  "description": "Custom metadata to attach to the inbox.",
-  "title": "Metadata",
-  "type": "object"
-}
    • removedInput schema / properties / status
      Removed value: -{
-  "description": "Set `paused` to create the inbox paused.",
-  "enum": [
-    "active",
-    "paused"
-  ],
-  "title": "InboxStatus",
-  "type": "string"
-}
    • removedInput schema / properties / username
      Removed value: -{
-  "description": "Username of address. Randomly generated if not specified.",
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • removedInput schema / properties / metadata / additionalProperties / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "format": "double",
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / metadata / additionalProperties / oneOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "format": "double",
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
  3. Changed4 schema fields changed
    • removedInput schema / properties / Authorization
      Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}
    • changedInput schema / properties / domain / description
      Previous value: -"Domain of address. Must be verified domain. Defaults to `agentmail.to`."New value: +"Domain of address. Must be a verified domain, or any subdomain of a\nverified domain that has subdomains enabled (e.g., `bot.example.com`).\nDefaults to `agentmail.to`."
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Set `paused` to create the inbox paused.",
+  "enum": [
+    "active",
+    "paused"
+  ],
+  "title": "InboxStatus",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "Authorization"
-]New value: +[]
  4. Changed4 schema fields changed
    • addedInput schema / properties / Authorization
      Added value: +{
+  "description": "Bearer authentication",
+  "type": "string"
+}
    • changedInput schema / properties / domain / description
      Previous value: -"Domain of address. Must be a verified domain, or any subdomain of a\nverified domain that has subdomains enabled (e.g., `bot.example.com`).\nDefaults to `agentmail.to`."New value: +"Domain of address. Must be verified domain. Defaults to `agentmail.to`."
    • removedInput schema / properties / status
      Removed value: -{
-  "description": "Set `paused` to create the inbox paused.",
-  "enum": [
-    "active",
-    "paused"
-  ],
-  "title": "InboxStatus",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "Authorization"
+]
  5. Changed4 schema fields changed
    • removedInput schema / properties / Authorization
      Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}
    • changedInput schema / properties / domain / description
      Previous value: -"Domain of address. Must be verified domain. Defaults to `agentmail.to`."New value: +"Domain of address. Must be a verified domain, or any subdomain of a\nverified domain that has subdomains enabled (e.g., `bot.example.com`).\nDefaults to `agentmail.to`."
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Set `paused` to create the inbox paused.",
+  "enum": [
+    "active",
+    "paused"
+  ],
+  "title": "InboxStatus",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "Authorization"
-]New value: +[]
  6. First observed

TDQS

C2.8/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 readOnlyHint=false, so the description should add context about the write path — e.g. that creation is irreversible, requires a verified domain, or what the response contains. Instead it advertises 'pagination support' that no parameter in the schema exposes, which is at best unbacked behavior disclosure.

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 core is a single front-loaded sentence with no filler, which is good. However, cramming two distinct operations into one clause without a discriminator hurts scannability, and the injected pricing block adds text that does not help tool selection.

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?

For a tool with a nested 6-field request body, destructive creation semantics, and a dual list/create mode, the description omits the mode discriminator, prerequisites (verified domain / subdomain enablement), and the pagination parameters it advertises. The output schema covers return values, but the invocation contract is under-explained.

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?

Only one top-level parameter exists, and its nested properties (domain, status, metadata, username, client_id, display_name) are already well documented inside the schema. The description restates three of those field names but adds no syntax, defaults, or constraint detail beyond what the schema provides, so it sits at the documented baseline.

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 states two concrete verb+resource operations (list inboxes, create an inbox) and names the creatable fields, so the tool's function is clear. It stops short of distinguishing itself from the sibling get_agentmail_inboxes, which also lists inboxes, leaving genuine routing ambiguity between the two.

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 this tool versus get_agentmail_inboxes for listing, nor any explanation of what selects list mode versus create mode (presumably the presence of `body`, but that is never stated). The agent is left to infer the trigger condition for a dual-behavior tool.

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