Skip to main content
Glama

Create a creative

lob_creatives_create
Idempotent

Create campaign creatives for postcards, letters, or self-mailers by providing Lob template IDs for each required side. Specify campaign ID and resource type.

Instructions

Create a campaign creative — the artwork (front/back / inside/outside / file) used by a campaign for postcards, letters, or self-mailers. Important: unlike lob_postcards_create and the other mail-piece create tools, Lob's /v1/creatives endpoint does NOT accept HTML strings, remote URLs, or inline PDFs in the content fields — it accepts ONLY a Lob template ID (tmpl_…). To use a URL or HTML as creative content, first call lob_templates_create to upload it as a template, then pass the resulting tmpl_… here. Required by resource_type: postcard → front + back; letter → file + from; self_mailer → inside + outside. Live-mode key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesParent campaign ID.
resource_typeYes
frontNoPostcard creative front: a Lob template ID (`tmpl_…`). Required for postcard creatives.
backNoPostcard creative back: a Lob template ID (`tmpl_…`). Required for postcard creatives.
insideNoSelf-mailer creative inside: a Lob template ID.
outsideNoSelf-mailer creative outside: a Lob template ID.
fileNoLetter creative file: a Lob template ID. Required for letter creatives.
detailsNoResource-specific options. Per Lob's spec, accepted keys for postcard creatives are `mail_type` (usps_first_class | usps_standard) and `size` (4x6 | 6x9 | 6x11). For letters: `mail_type`, `color`, `double_sided`, `address_placement`, `extra_service`. Empty `{}` is valid.
descriptionNo
fromNoSender address — saved address ID (`adr_…`) or inline. Required for letter creatives.
metadataNoUp to 20 string key/value pairs of arbitrary metadata to attach to the resource.
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.
Behavior5/5

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

Annotations are consistent; description adds critical behavioral details: only template IDs accepted, required fields per type, live-mode key required. No contradiction.

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, front-loaded with core purpose, no unnecessary words. Efficient and informative.

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?

Covers main constraints and required fields, but lacks return value description (no output schema exists). Could mention error cases or rate limits, but overall sufficient given complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema: explains that front/back/inside/outside/file must be tmpl_ IDs, and describes details parameter's accepted keys per resource type. Schema coverage is high but description enriches context.

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?

Description clearly states the tool creates a campaign creative (artwork) for postcards, letters, or self-mailers. It distinguishes from sibling tools by highlighting the key constraint that only Lob template IDs are accepted.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly contrasts with lob_postcards_create etc., noting they accept HTML/URLs while this tool requires template IDs. Provides alternative workflow: call lob_templates_create first. Also specifies required fields per resource_type.

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