Skip to main content
Glama
Achlesha

sendhustle-mcp

by Achlesha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

send_batch_emails

Send up to 100 emails in one request by providing an array of email objects with recipient, subject, and content. Streamline bulk email delivery with a single API call.

Instructions

Send up to 100 emails in one request (POST /emails/batch). Pass an array of email objects, each with from/to/subject and html and/or text. Per-email "from" defaults to the configured sender if omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailsYesArray of email objects (max 100). Each: from, to, subject, html/text, plus optional cc/bcc/reply_to/scheduled_at/tags/headers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses the batch limit, the HTTP endpoint, and the per-email 'from' defaulting behavior. However, it does not mention side effects beyond sending, partial failure behavior, idempotency, or rate-limit implications.

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 sentences, no filler. The most important facts are front-loaded: the action, the batch limit, and the endpoint come first, followed by payload structure and a useful default behavior.

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?

For a single-parameter tool with a well-described schema, the description covers the essentials: endpoint, payload shape, limit, and default behavior. A response/error-behavior note would improve completeness, but an agent has enough to invoke this tool correctly.

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?

Schema coverage is already 100%, so the baseline is 3. The description adds valuable semantics beyond the schema by clarifying that each email should include from/to/subject and html and/or text, and by explaining the 'from' default when omitted.

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 states a specific action ('Send'), a clear resource ('up to 100 emails in one request'), and the endpoint (POST /emails/batch). This distinguishes it from send_email and other sibling tools without needing to inspect 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?

The batch context is clear: this tool is for sending multiple emails in one request, with an explicit cap of 100. It does not explicitly mention when not to use it or point to send_email as the single-email alternative, but the usage context is unambiguous enough for selection.

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