Skip to main content
Glama

agent-cold-email

by io.github.YS-projectcalc

get_byo_domains

Read-only

List your BYO (bring-your-own) domains, or (with id) one domain's full intake detail. No id → [{ domainId, domain, isPrimary, dnsMode, byoStatus, breakerTier, reputationBranch, mailboxCount }]. With id → adds the pre-flight scan result, abuse-gate verdict, and consent-acknowledgment status. byoStatus progresses pending_kyc|pending_consent|pending_dns → active (or rejected/abandoned). Use configure_byo_domain to register a new one or advance it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOmit to list every BYO domain; pass an id for that domain's full intake detail (scan result, abuse verdict, consent status).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true. Beyond that, the description enriches transparency by detailing the output fields for both cases, the progression of byoStatus, and the additional data returned with an id. No contradictions.

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?

Front-loaded with main purpose, then efficiently covers output differences, status progression, and sibling tool reference. Every sentence adds value with no waste.

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?

Despite lacking an output schema, the description fully explains return values for both invocation patterns, status lifecycle, and the relationship to the sibling tool. Complete for a read-only list/detail tool.

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 clear explanation of the 'id' parameter. The description restates the same semantics without adding new parameter-specific meaning, meeting baseline for high coverage.

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 verb 'List' and the resource 'BYO domains', and distinguishes two use cases (listing all vs. getting full detail with id). It differentiates from sibling tool 'configure_byo_domain' which is for registration/advancement.

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

Usage Guidelines5/5

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

Explicitly tells when to use the sibling tool 'configure_byo_domain' instead ('to register a new one or advance it'), providing clear alternative guidance for the agent.

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

All agent-cold-email toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Most tools have distinct purposes, but pause/pause_all and metrics/campaign_results/list_campaigns have overlapping scopes. Descriptions clarify the differences, so ambiguity is low.

Naming Consistency4/5

Uses snake_case with a mix of verb_noun (list_campaigns) and noun_verb (infrastructure_status), but patterns are predictable. Minor inconsistency between setup_infrastructure and infrastructure_status.

Tool Count4/5

25 tools is at the upper bound for a focused server, but the domain (cold email automation) justifies the number. Each tool covers a distinct aspect of the workflow.

Completeness4/5

Covers account management, campaigns, leads, threads, infrastructure, webhooks, and dashboards. Missing resume for paused campaigns and delete for campaigns, but core operations are present.

Resources