Skip to main content
Glama
optimize-overseas

lob-mcp

by optimize-overseas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a postcard (BILLABLE)

lob_postcards_create
DestructiveIdempotent

Create and send a physical postcard via Lob API. Provide to, from, front, and back; requires confirmation token in live mode.

Instructions

Commit a postcard send. Billable in live mode: produces real physical mail and is charged to your Lob account. In live mode, requires a confirmation_token from lob_postcards_preview that matches the current payload. In test mode, the token is optional (dev ergonomics).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient address. Either a saved address ID (`adr_…`) or an inline address.
backYesBack-of-postcard content source.
fromYesSender (return) address. Either a saved address ID (`adr_…`) or an inline address.
sizeNoPostcard size. Defaults to 4x6.
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.
frontYesFront-of-postcard 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_postcards_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?

Over annotations (destructiveHint=true, idempotentHint=true), the description adds that the tool is billable in live mode and produces real physical mail. It also explains the token requirement. 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?

Three sentences that are concise and front-loaded. Every sentence provides essential information without redundancy.

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?

Given 15 parameters and no output schema, the description covers key behavioral context (billing, preview requirement, mode differences). It is sufficient for an agent to use correctly, though more detail on content sources could help.

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% and the description adds no new parameter details beyond the schema. The baseline of 3 applies as the description does not enhance parameter understanding.

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 title and description clearly state the tool creates a postcard and commits a send. It explicitly mentions billing and the relationship with the preview step (lob_postcards_preview), distinguishing it from sibling tools like lob_postcards_preview.

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 explains when to use the tool (after preview, to commit) and clarifies mode-dependent behavior (live requires confirmation_token, test optional). It does not list alternatives but the context is clear.

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