Skip to main content
Glama

Create a letter (BILLABLE)

lob_letters_create
DestructiveIdempotent

Send a physical letter to a recipient via Lob. Requires confirmation token after preview for production delivery.

Instructions

Commit a letter send. Billable in live mode. Requires a confirmation_token from lob_letters_preview that matches the current payload (live mode only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoInternal description (max 255 chars).
toYesRecipient address. Either a saved address ID (`adr_…`) or an inline address.
fromYesSender (return) address. Either a saved address ID (`adr_…`) or an inline address.
send_dateNoISO 8601 timestamp (e.g. '2026-05-01T00:00:00Z') to schedule the send. Must be at most 180 days in the future.
mail_typeNoMail class. Defaults to usps_first_class for most pieces.
merge_variablesNoKey/value pairs substituted into Handlebars-style {{variables}} in your HTML/template content.
metadataNoUp to 20 string key/value pairs to attach to the resource.
billing_group_idNoBilling group ID (`bg_…`) to attribute the charge to.
use_typeNoRequired for some mail classes. 'marketing' for promotional, 'operational' for transactional.
fileYesLetter body content source (HTML, URL, template ID, or base64 PDF).
colorNoPrint in color (true) or black-and-white (false). Affects pricing.
double_sidedNoPrint on both sides. Defaults to true for letters.
address_placementNoWhere the recipient address window appears on a letter.
return_envelopeNoInclude a return envelope. Boolean true for default, or a return envelope ID.
perforated_pageNoPage number to perforate (used with return_envelope).
custom_envelopeNoCustom envelope reference for letters/checks.
extra_serviceNoUSPS extra service add-on. Affects pricing and delivery time.
cardsNoCard IDs (`card_…`) to insert. Up to 4.
buckslipsNoBuckslip references to insert.
idempotency_keyNoIdempotency key (max 256 chars). If omitted, the server auto-generates a value derived from the confirmation_token when present, otherwise a fresh UUIDv4. Lob deduplicates identical keys for 24 hours.
extraNoAdditional Lob API parameters not enumerated above. Merged into the request body verbatim. See https://docs.lob.com for the full parameter list per resource.
confirmation_tokenNoToken from lob_letters_preview. Required in live mode (LOB_LIVE_MODE=true).
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, but the description adds confirmation_token requirement and billing note. However, it does not explain the consequence of creating (e.g., cost consumption) or the idempotency behavior. The description provides minimal behavioral context beyond what annotations convey.

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?

The description is extremely concise—two clear sentences that convey the core purpose and key constraint. No wasted words, front-loaded with the action. Ideal conciseness for a tool with strong annotations and schema.

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

Completeness2/5

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

Despite having 22 parameters and no output schema, the description omits many crucial details: what the response contains (presumably a Letter object), error conditions, validation rules, and the workflow to use confirmation_token. It is incomplete for the complexity level.

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?

With 100% schema description coverage, the baseline is 3. The description adds marginal semantic value by stressing the confirmation_token requirement and its relation to preview, but this is already in the schema. No other parameter meanings are enhanced.

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 action ('Commit a letter send') and explicitly distinguishes from sibling lob_letters_preview by requiring a confirmation token from that preview tool. It also highlights that it is billable in live mode, which is a key distinguishing trait.

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 implies a workflow: use lob_letters_preview first to obtain confirmation_token, then use this tool to commit. It specifies that confirmation_token is required in live mode, but does not explicitly mention when not to use or provide alternative tools. The guidance is clear but lacks exclusions.

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/optimize-overseas/lob-mcp'

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