Skip to main content
Glama

Preview a postcard

lob_postcards_preview
Idempotent

Preview a postcard design without being charged. Generate a confirmation token for use when creating the final postcard.

Instructions

Render a Lob proof PDF for a postcard without charging or sending. Returns a confirmation_token to pass to lob_postcards_create. The token is required in live mode (LOB_LIVE_MODE=true). Token TTL: LOB_CONFIRMATION_TTL_SECONDS (default 600). Sizes: 4x6 (default), 6x9, 6x11.

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.
frontYesFront-of-postcard content source.
backYesBack-of-postcard content source.
sizeNoPostcard size. Defaults to 4x6.
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.
Behavior4/5

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

Annotations (idempotentHint, readOnlyHint false, destructiveHint false) are consistent. The description adds context about the token's purpose and TTL, and clarifies the non-charging nature. It does not discuss rate limits or authentication but is fairly transparent.

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 concise sentences with no wasted words. The core purpose, token usage, and sizes are front-loaded and clear.

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 14 parameters and no output schema, the description adequately covers the workflow token, TTL, sizes, and non-charging aspect. It could mention response structure but the token is sufficient for an agent.

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 100%, so the description need not repeat. It adds value by explaining the token's role in the creation workflow and the significance of the size parameter beyond enum values.

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 name clearly indicate previewing a postcard. The description states it renders a proof PDF without charging or sending, distinguishing it from lob_postcards_create and other preview tools for different resources.

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 using this tool before creation in live mode by mentioning the confirmation token passed to lob_postcards_create and the token TTL. However, it does not explicitly state when to use versus when to skip.

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