Skip to main content
Glama
Quolle MCP

Quolle MCP

by Quolle-main

Send a batch of emails

send_batch

Send up to 100 emails in a single all-or-nothing request, letting you batch transactional sends while each item uses the same fields as an individual email.

Instructions

Send up to 100 emails in one all-or-nothing request (no attachments in a batch). Each item takes the same fields as send_email.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "emails": "<emails>"
    },
    "name": "send_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYesThe emails to send.
idempotencyKeyNoSame key = same result, never a second send.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / emails / description
      Previous value: -"Array of email payloads."New value: +"The emails to send."
    • removedInput schema / properties / emails / items / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / emails / items / properties
      Added value: +{
      +  "from": {
      +    "description": "Sender, e.g. \"Acme <hello@mail.acme.com>\". Its domain must be verified (see list_domains).",
      +    "type": "string"
      +  },
      +  "html": {
      +    "description": "HTML body. Use html OR template, not both.",
      +    "type": "string"
      +  },
      +  "metadata": {
      +    "additionalProperties": {},
      +    "description": "Your own key/values, echoed back in webhooks.",
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "replyTo": {
      +    "description": "Reply-To address.",
      +    "type": "string"
      +  },
      +  "scheduledAt": {
      +    "description": "ISO 8601 time to send later, e.g. 2026-12-25T09:00:00Z.",
      +    "type": "string"
      +  },
      +  "subject": {
      +    "description": "Subject line (required when sending html).",
      +    "type": "string"
      +  },
      +  "template": {
      +    "description": "Slug of a saved template. Use template OR html, not both.",
      +    "type": "string"
      +  },
      +  "text": {
      +    "description": "Optional plain-text body (generated from html if omitted).",
      +    "type": "string"
      +  },
      +  "to": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "items": {
      +          "type": "string"
      +        },
      +        "maxItems": 50,
      +        "minItems": 1,
      +        "type": "array"
      +      }
      +    ],
      +    "description": "Recipient address, or up to 50 addresses."
      +  },
      +  "variables": {
      +    "additionalProperties": {},
      +    "description": "Template variables.",
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  }
      +}
    • addedInput schema / properties / emails / items / required
      Added value: +[
      +  "from",
      +  "to"
      +]
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "description": "Same key = same result, never a second send.",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, open-world operation, and the description adds the critical behavioral traits: all-or-nothing execution, a 100-email cap, and no attachment support in batches. It does not mention idempotencyKey semantics or response behavior, but the added atomicity disclosure is substantial beyond the annotations.

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?

Two sentences, both front-loaded with the most important constraints, and no wasted text. The atomicity and attachment limitation are stated immediately.

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 batch-send tool with a fully described input schema and meaningful annotations, the description covers the key invocation constraints. It is slightly incomplete because there is no output schema and the description does not describe the response or idempotency behavior, but it is sufficient for correct selection and invocation.

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 the nested item fields are already fully documented. The description adds a useful cross-reference that each item matches send_email's fields, but does not elaborate on idempotencyKey or add syntax 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 states a specific verb and resource ('Send up to 100 emails') and adds the distinguishing scope 'in one all-or-nothing request'. It clearly separates this batch tool from the single-email sibling send_email without naming it explicitly.

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?

It gives clear context for when to use a batch send: multiple emails, atomicity, and no attachments. It does not explicitly say 'use send_email for single emails or attachments', but that alternative is strongly implied by the attachment exclusion and the reference to send_email's fields.

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