Skip to main content
Glama

configure_byo_domain

Destructive

Configure a custom domain for cold email sending: register domain, verify DNS, acknowledge consent, request managed mailboxes, or connect existing email accounts.

Instructions

Register or advance a BYO domain/mailbox intake (SPEC.md §20). action = register (needs domain + domainRelationship: fresh_standalone|subdomain_of_primary|is_primary — runs the pre-flight live-infra scan + abuse gate + reputation ladder, returns the starting byoStatus) | poll_dns (needs id — re-checks DNS delegation/records, advances pending_dns → active, or → abandoned after 7 idle days) | acknowledge_consent (needs id + acknowledged:true — REQUIRED before a primary domain can proceed past pending_consent; this does not remove your business's exposure, it documents informed consent) | request_managed_mailboxes (needs id + count — platform-provisioned mailboxes on an ALREADY-ACTIVE domain, the primary shape; every response carries a billing projection { provisionedAfter, projectedMonthlyCents, formula } — quoteOnly:true previews it without provisioning) | connect_mailbox (needs id + email + transport — declares an EXISTING OAuth/SMTP+IMAP connection you already have, bypassing provisioning; transport is { kind:'smtp', host, port, secure, user, pass } | { kind:'gmail_api', clientId, clientSecret, refreshToken } | { kind:'ms_graph', mode, tenantId, clientId, clientSecret, refreshToken? }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoRequired for poll_dns/acknowledge_consent/request_managed_mailboxes/connect_mailbox — the domainId from register.
countNoRequired for request_managed_mailboxes — how many platform-provisioned mailboxes to attach.
emailNoRequired for connect_mailbox — the existing mailbox address.
actionYes
domainNoRequired for register.
quoteOnlyNoOptional for request_managed_mailboxes — true previews the new mailbox count + projected monthly price WITHOUT provisioning (SPEC §18 quote-before-add).
transportNoRequired for connect_mailbox — { kind: 'smtp', host, port, secure, user, pass } | { kind: 'gmail_api', clientId, clientSecret, refreshToken } | { kind: 'ms_graph', mode: 'delegated'|'app_only', tenantId, clientId, clientSecret, refreshToken? }.
personaSlugNoOptional for request_managed_mailboxes — defaults to a slug of the domain.
acknowledgedNoRequired (must be true) for acknowledge_consent — SPEC.md §20.4's separate, unbundled risk acknowledgment.
domainRelationshipNoRequired for register: fresh_standalone | subdomain_of_primary | is_primary.
Behavior4/5

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

The description adds behavioral context beyond the destructiveHint annotation, such as running a 'pre-flight live-infra scan + abuse gate + reputation ladder' and returning billing projections. It does not contradict the annotation and enriches understanding of side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but well-structured with action identifiers and clear sentences. It is as concise as possible given the tool's complexity, front-loading the overall purpose before detailing each action.

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

Completeness5/5

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

The description covers all actions, parameter dependencies, billing projection behavior, and special flags like quoteOnly. With no output schema, it provides sufficient context for an AI agent to invoke the tool correctly across all scenarios.

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

Parameters4/5

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

With 90% schema description coverage, the baseline is 3. The description adds meaning by explaining each parameter's role per action (e.g., 'acknowledge_consent needs id + acknowledged:true — REQUIRED before a primary domain can proceed past pending_consent'), going beyond the schema.

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?

The description clearly states the tool is for registering or advancing BYO domain/mailbox intake, referencing SPEC.md §20. It lists five distinct actions with specific verbs and resources, effectively distinguishing each sub-operation.

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?

The description provides detailed guidance on when to use each action, including required parameters and context (e.g., 'register needs domain + domainRelationship', 'poll_dns needs id'). It implies a logical order but does not explicitly compare against sibling tools or state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YS-projectcalc/agent-cold-email'

If you have feedback or need assistance with the MCP directory API, please join our Discord server