Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Email Sending Domains

list-email-domains
Read-onlyIdempotent

List your organization's sending domains and their verification status to confirm which addresses can be used as a campaign's from address.

Instructions

List the organization's sending domains and their verification status. Any address at a verified domain can be an email campaign's from. Register a new one with create-email-domain. Don't read ids or timestamps back to the user unless they ask for them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-email-domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoCursor for the next page: the `id` of the last item on this page. Cannot be combined with `before`.
limitNoItems per page, 1-100. Defaults to 20.
beforeNoCursor for the previous page: the `id` of the first item on this page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new context: what 'verified' means operationally (a verified domain can serve as a campaign's `from`) and a presentation rule about not surfacing ids or timestamps unprompted. It does not discuss pagination or ordering, which the schema partially covers.

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?

Three short sentences, front-loaded with purpose, then the semantic definition of verification, then the sibling hand-off, then the display caveat. No redundant restatement of the title or annotations.

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?

A read-only list tool with three fully documented optional pagination parameters and no output schema needs little more than this; the description covers purpose, domain-status meaning, and the create alternative. Minor gap: no mention of result ordering or page-size defaults, though the schema supplies defaults.

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%, so cursor and limit semantics are already fully documented in the input schema. The description adds nothing about parameters, which is acceptable at this coverage level but earns only the baseline.

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

Purpose5/5

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

States a specific verb and resource ('List the organization's sending domains') plus the scope of returned data ('their verification status'), which distinguishes it from get-email-domain and list-email-campaigns. An agent can identify the tool's output subject without opening the schema.

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

Usage Guidelines4/5

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

Explicitly routes the creation case to create-email-domain ('Register a new one with create-email-domain'), giving a clear alternative for the adjacent intent. It does not state exclusions for single-domain lookup (get-email-domain), so it falls short of a full when/when-not treatment.

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