Groundmail

List domains

list_domains

Read-onlyIdempotent

List sending domains for this account.

Input Schema

Name	Required	Description
`limit`	No	Page size (1–100)
`cursor`	No	Opaque cursor for the next page
`tenant`	No	Only domains this tenant owns. The tenant's external id (your id for that customer) or its Groundmail id

Output Schema

Name	Required	Description
`domains`	Yes	Sending domains on this page
`has_more`	No	True when another page of results is available
`next_cursor`	No	Cursor to pass as `cursor` to fetch the next page; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / domains / items / properties / blocklists

Added value: +{
+  "description": "Daily check of the domain and its main domain on Spamhaus DBL, SURBL and URIBL. A listing never pauses sending",
+  "properties": {
+    "checked_at": {
+      "description": "When the last daily blocklist check ran (ISO 8601)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "listings": {
+      "description": "Current listings, main domain first",
+      "items": {
+        "properties": {
+          "info_url": {
+            "description": "Where to look the name up and request removal",
+            "type": "string"
+          },
+          "list": {
+            "description": "List name: Spamhaus DBL, SURBL or URIBL",
+            "type": "string"
+          },
+          "list_id": {
+            "description": "List id: spamhaus-dbl, surbl or uribl",
+            "type": "string"
+          },
+          "listed_since": {
+            "description": "When the daily check first found it listed (ISO 8601)",
+            "type": "string"
+          },
+          "name": {
+            "description": "The listed name: the domain itself or its main domain",
+            "type": "string"
+          },
+          "reason": {
+            "description": "What the list says it is listed for, for example spam domain",
+            "type": "string"
+          }
+        },
+        "required": [
+          "list",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "main_domain": {
+      "description": "The main (registrable) domain",
+      "type": "string"
+    },
+    "names": {
+      "description": "Names checked: the domain and its main domain, or one name for a main domain",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "removed": {
+      "description": "Recent removals, newest first",
+      "items": {
+        "properties": {
+          "info_url": {
+            "description": "Where to look the name up and request removal",
+            "type": "string"
+          },
+          "list": {
+            "description": "List name: Spamhaus DBL, SURBL or URIBL",
+            "type": "string"
+          },
+          "list_id": {
+            "description": "List id: spamhaus-dbl, surbl or uribl",
+            "type": "string"
+          },
+          "listed_since": {
+            "description": "When the daily check first found it listed (ISO 8601)",
+            "type": "string"
+          },
+          "name": {
+            "description": "The listed name: the domain itself or its main domain",
+            "type": "string"
+          },
+          "reason": {
+            "description": "What the list says it is listed for, for example spam domain",
+            "type": "string"
+          },
+          "removed_at": {
+            "description": "When it came off the list (ISO 8601)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "list",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "Blocklist status: clear, listed, or unknown (not checked yet, not verified, or no list answered)",
+      "type": "string"
+    },
+    "unanswered_lists": {
+      "description": "Lists that did not answer the last check",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / tenant

Added value: +{
+  "description": "Only domains this tenant owns. The tenant's external id (your id for that customer) or its Groundmail id",
+  "type": "string"
+}

addedOutput schema / properties / domains / items / properties / tenant

Added value: +{
+  "description": "External id of the tenant that owns the domain. Absent for a domain the whole account can use",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedOct 16, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the account scope and says nothing about pagination behavior, default page size, or ordering, leaving it with almost no value beyond the structured fields.

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 front-loaded sentence with zero filler for a simple list operation. Nothing is redundant or buried.

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

Completeness3/5

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

An output schema exists and all three parameters are described, so the description needn't explain return values or pagination mechanics. However, it is thin enough that an agent gets no signal about how the account scope relates to the tenant filter or whether results are paginated by default.

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 description coverage is 100%, with limit, cursor, and tenant each documented, so the baseline is 3. The description adds no further meaning about how the tenant filter interacts with the account scope, so it neither helps nor harms.

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 specific verb and resource ('List sending domains') with an account scope, which cleanly separates it from the mutating siblings create_domain, verify_domain, and apply_domain_dns. It stops short of naming those siblings, so differentiation relies on the verb alone.

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 explicit when-to-use, when-not-to-use, or alternative routing; the only hint is the phrase 'for this account.' An agent must infer from the name that this is the read path versus create_domain or get_tenant.

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

All Groundmail tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.