InkFE Print

Create a business card design

create_business_card_design

Idempotent

Applies the buyer's field values (and logo, if the template needs one) to a template, fits the text to its printable area, renders both sides as preview images, and returns a design token. Before creating a guest design, explain: unpaid, unsaved drafts expire 30 days after the design request starts. Verified saving keeps the draft; checkout and unresolved purchase artwork is protected. Seven-day token expiry is separate from deletion. Call list_business_card_templates first and collect a non-blank value for every field it lists, keyed by attribute; a blank or missing value fails with missing_required_fields. Pass a public https PNG or JPEG URL as logoUrl only when the template has an imageUrl field; omit it otherwise. Returns designToken, designId, templateId, revisionId, expiresAt (7 days out), previews (a 300-second signed URL plus width/height for each side; the pixels are also attached as image content blocks), and any text_shrunk warnings from fitting a value to its layer. Present both attached proof images directly, or provide labeled front/back links to the exact preview URLs if the host cannot display them. Do not require computer setup, downloads or re-uploading for proof review. Refresh expired links rather than creating another design. An accountOwned result identifies a verified customer, not an integration key. Results also include a private saveUrl for browser ownership verification; offer it only when the buyer wants to save. Saving requires sign-in; subsequent checkout of that design requires an AI connection authorized by the same InkFE account. If customer OAuth is unavailable, complete checkout before saving. Use a stable requestId; retry the same request after a timeout. Revise with revise_business_card_design and refresh expired links with refresh_design_proof. Show both previews and warnings, get exact print options and get_quote, then record explicit customer approval with approve_design_proof before create_checkout. Fails with unknown_template, missing_required_fields {attributes}, unknown_field {attribute}, value_too_long {attribute}, unsupported_characters {attribute}, logo_required, logo_fetch_failed, logo_unsupported, rate_limited {retryAfterSeconds} (too many designs from this API key in a short time), or connector_unavailable.

Input Schema

Name	Required	Description
`fields`	Yes	Every attribute from the chosen template's `fields` list (see list_business_card_templates) is required, keyed by `attribute`, with the buyer's text for it. Do not include the logo field here: pass its image via logoUrl instead. A blank or missing value fails with missing_required_fields.
`logoUrl`	No	A public https URL to a PNG or JPEG logo image, required only when the template has an imageUrl field (see list_business_card_templates). Omit it for every other template.
`requestId`	Yes	A new stable requestId for each intentional design/revision. Reuse the same id and inputs after a timeout; never automatically replace an in-progress request.
`guestToken`	No	Private guestToken from start_guest_session, required only for anonymous guest design and checkout. Omit when connected through InkFE customer sign-in (OAuth) or a provisioned integration key; those connections must not start a guest session. Keep guest tokens in this conversation; never put them in a URL or share them.
`templateId`	Yes	The templateId from list_business_card_templates identifying which Classic business card to design.

Output Schema

Name	Required	Description
`proof`	Yes	Immutable proof identity used by approval.
`saveUrl`	No	Private browser link to save the design to an InkFE account.
`designId`	Yes
`nextStep`	Yes
`previews`	Yes	Front and back proof images; also attached as image content.
`warnings`	Yes	Fitting adjustments to show the buyer with the proofs.
`expiresAt`	Yes	When the designToken expires.
`revisionId`	Yes
`templateId`	Yes
`designToken`	Yes	Private token for this immutable design; keep in the conversation.
`accountOwned`	No	Present when a verified customer owns the design.
`draftRetention`	No	Present for guest drafts: how long an unsaved draft is kept.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "accountOwned": {
+      "const": true,
+      "description": "Present when a verified customer owns the design.",
+      "type": "boolean"
+    },
+    "designId": {
+      "type": "string"
+    },
+    "designToken": {
+      "description": "Private token for this immutable design; keep in the conversation.",
+      "type": "string"
+    },
+    "draftRetention": {
+      "description": "Present for guest drafts: how long an unsaved draft is kept.",
+      "type": "string"
+    },
+    "expiresAt": {
+      "description": "When the designToken expires.",
+      "type": "string"
+    },
+    "nextStep": {
+      "type": "string"
+    },
+    "previews": {
+      "description": "Front and back proof images; also attached as image content.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "expiresInSeconds": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "height": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "side": {
+            "enum": [
+              "front",
+              "back"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "description": "Short-lived signed preview URL.",
+            "type": "string"
+          },
+          "width": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "side",
+          "url",
+          "expiresInSeconds"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "proof": {
+      "additionalProperties": {},
+      "description": "Immutable proof identity used by approval.",
+      "properties": {
+        "artifactHash": {
+          "description": "Lowercase hex SHA-256 digest.",
+          "type": "string"
+        },
+        "previews": {
+          "additionalProperties": {},
+          "properties": {
+            "back": {
+              "description": "Lowercase hex SHA-256 digest.",
+              "type": "string"
+            },
+            "front": {
+              "description": "Lowercase hex SHA-256 digest.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "front",
+            "back"
+          ],
+          "type": "object"
+        },
+        "version": {
+          "const": 1,
+          "type": "number"
+        }
+      },
+      "required": [
+        "version",
+        "artifactHash",
+        "previews"
+      ],
+      "type": "object"
+    },
+    "revisionId": {
+      "type": "string"
+    },
+    "saveUrl": {
+      "description": "Private browser link to save the design to an InkFE account.",
+      "type": "string"
+    },
+    "templateId": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "warnings": {
+      "description": "Fitting adjustments to show the buyer with the proofs.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "attribute": {
+            "type": "string"
+          },
+          "code": {
+            "description": "e.g. \"text_shrunk\".",
+            "type": "string"
+          },
+          "fromFontSize": {
+            "type": "number"
+          },
+          "layerId": {
+            "type": "string"
+          },
+          "toFontSize": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "attribute",
+          "layerId",
+          "code",
+          "fromFontSize",
+          "toFontSize"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "designToken",
+    "designId",
+    "templateId",
+    "revisionId",
+    "proof",
+    "expiresAt",
+    "previews",
+    "warnings",
+    "nextStep"
+  ],
+  "type": "object"
+}

First observedSep 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare idempotentHint=true, readOnlyHint=false, and destructiveHint=false. The description adds substantial behavioral context beyond those: 30-day expiry for unpaid guest drafts, seven-day token expiry, 300-second signed preview URLs, text_shrunk warnings, accountOwned semantics, private saveUrl ownership verification, and a full list of failure modes. It also explains retry behavior with a stable requestId, which aligns with and enriches the idempotency hint.

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 description is long but every sentence earns its place: it covers prerequisites, parameter semantics, return values, follow-up actions, and failure modes. It is front-loaded with the core action and then layers context. The only minor deduction is that the failure-mode list is dense and could be slightly more scannable, but it is not redundant.

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?

Given the tool's complexity (5 params, nested fields, output schema, 10 siblings), the description is remarkably complete. It covers prerequisites, parameter semantics, return values, error handling, retry behavior, and the exact downstream workflow. The output schema exists, so the description needn't restate return types, but it still adds the 300-second preview URL detail and text_shrunk warnings.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains that fields must be keyed by `attribute`, that blank or missing values fail with missing_required_fields, that logoUrl must be a public https PNG/JPEG and only when the template has an imageUrl field, and that guestToken is only for anonymous guest sessions. It also clarifies the relationship between requestId and retry behavior, which the schema only hints at.

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: it applies buyer field values and an optional logo to a template, fits text, renders both sides as previews, and returns a design token. It clearly distinguishes this from siblings like revise_business_card_design and refresh_design_proof by naming them as follow-up actions rather than alternatives.

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?

The description gives explicit when-to-use guidance: call list_business_card_templates first, collect a non-blank value for every field, pass logoUrl only when the template has an imageUrl field, and omit it otherwise. It also names the exact follow-up sequence (revise, refresh, get_quote, approve, create_checkout) and warns against creating another design when links expire.

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

All InkFE Print tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?