Skip to main content
Glama

postedly_design_postcard

Creates a two-page postcard document without a PDF: the front is a ready-made design, a photo-frame design with the sender's photo placed in its photo area, or a custom front image covering the whole front, and the back carries a typed message that Postedly sets in a fixed typeface in the left column, clear of the address and postage area. Images are JPEG or PNG (PNG at most 4 megapixels; use a JPEG for larger pictures), sent as base64 or as the ID of an image uploaded for a postcard; they are centered and cropped to fill, and images too small for good quality, far from the target shape, or text that does not fit is rejected with a specific error rather than shrunk. Returns a private document ID, page count, SHA-256, an authenticated preview URL, what was composed and the postcard price. Does not create a quote, take payment or send anything.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "postedly_design_postcard"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesPlain text for the back, up to 450 characters that must also fit the message area: 15 lines of about 30 characters with a greeting and signature, 18 without. Line breaks are kept and each uses a line. Latin letters, digits and common punctuation; emoji and non-Latin scripts are rejected.
designIdNoDesign ID from the postcard product list. A photo-frame design also needs an image. Omit to use the image as the whole front.
greetingNoOptional opening line above the message, such as Dear Sam, up to 30 characters on one line; wide letters or all capitals fit fewer (LINE_TOO_WIDE).
signatureNoOptional closing line below the message, such as Love, Alex, up to 30 characters on one line; wide letters or all capitals fit fewer (LINE_TOO_WIDE).
imageBase64NoStandard padded base64 of a JPEG or PNG, without a data URL prefix: the sender's photo for a photo frame, or the whole front when designId is omitted. The sender's own or licensed image; a generated front is artwork with no words, since Postedly sets the message as type.
imageSha256NoOptional SHA-256 of the original image bytes; a mismatch rejects the request.
imageDocumentIdNoID of a JPEG or PNG already uploaded for a postcard, as an alternative to imageBase64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses a great deal: no PDF is produced, the message is set in a fixed typeface in the left column clear of the address area, oversized/off-shape/too-small inputs and overflowing text are rejected with specific errors rather than shrunk, and the return payload includes a private document ID, page count, SHA-256, authenticated preview URL and price. The rejection-rather-than-degrade policy is exactly the kind of behavior an agent cannot infer from schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The creation statement is front-loaded and every clause carries information — nothing is filler. The main weakness is structural: the core content is delivered as one very long, heavily nested sentence that an agent must parse in pieces, which costs some readability even though no words are wasted.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating the return fields (document ID, page count, SHA-256, preview URL, composition details, price). Combined with the input constraints, error behavior and explicit non-effects (no quote, no payment, no sending), an agent has everything needed to call this correctly for a moderately complex 7-parameter tool.

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 baseline is 3, but the description adds real meaning the schema does not: the interaction between designId and imageBase64/imageDocumentId (omit designId to use the image as the whole front; a photo-frame design requires an image), the PNG 4-megapixel ceiling with JPEG advised for larger pictures, and that images are centered and cropped to fill. Format guidance (base64 without a data URL prefix) is largely redundant with the schema.

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 opens with a specific verb and resource — 'Creates a two-page postcard document' — and immediately scopes what it produces (front design variants, typed back message) and what it does not do ('Does not create a quote, take payment or send anything'), which separates it from postedly_quote and postedly_checkout. An agent can identify the tool without opening the schema.

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 closing sentence gives explicit when-not guidance ('Does not create a quote, take payment or send anything'), implicitly routing pricing and sending to siblings. It also states a prerequisite-ish rule that a photo-frame design 'also needs an image'. What is missing is a positive routing statement naming the alternative to call for quoting or payment.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources