Skip to main content
Glama
optimize-overseas

lob-mcp

by optimize-overseas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a self-mailer (BILLABLE)

lob_self_mailers_create
DestructiveIdempotent

Commit a self-mailer send by providing inside and outside content, recipient, and sender addresses. Requires a confirmation token from preview in live mode.

Instructions

Commit a self-mailer send. Billable in live mode. Requires a confirmation_token from lob_self_mailers_preview that matches the current payload (live mode only). Sizes: 6x18_bifold (default), 11x9_bifold.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
sizeNoSelf-mailer size. Defaults to 6x18_bifold.
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.
insideYesInside-of-self-mailer content source.
outsideYesOutside-of-self-mailer content source.
metadataNoUp to 20 string key/value pairs to attach to the resource.
use_typeNoRequired for some mail classes. 'marketing' for promotional, 'operational' for transactional.
mail_typeNoMail class. Defaults to usps_first_class for most pieces.
send_dateNoISO 8601 timestamp (e.g. '2026-05-01T00:00:00Z') to schedule the send. Must be at most 180 days in the future.
descriptionNoInternal description (max 255 chars).
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.
merge_variablesNoKey/value pairs substituted into Handlebars-style {{variables}} in your HTML/template content.
billing_group_idNoBilling group ID (`bg_…`) to attribute the charge to.
confirmation_tokenNoToken from lob_self_mailers_preview. Required in live mode (LOB_LIVE_MODE=true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover mutability and idempotency. Description adds billing behavior (live mode only) and token requirement. Does not contradict 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?

Three sentences, front-loads critical info (commit, billable, token). No wasted words.

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 complex tool with many params and no output schema, description covers core purpose, billing, and token requirement. Schema descriptions fill remaining gaps.

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 covers 100% of parameters with descriptions. Description adds minimal extra, e.g., size defaults. Baseline 3 appropriate.

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?

States specific action: 'Commit a self-mailer send.' Distinct from preview, cancel, get, list. Includes billing context and size options.

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?

Clearly indicates prerequisite: requires confirmation_token from preview in live mode. Implicitly tells when to use (after preview) and when not (no token). No explicit alternatives but sibling preview exists.

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