InkFE Print

Revise a business card design

revise_business_card_design

Idempotent

Create a new immutable design from an authorized prior design, using the same published template revision. Supply the complete field set and logo where needed, not a partial patch. Use a new requestId for an intentional edit and the same id for retries. Returns both previews and a new designToken. Prior approval never approves the new revision; review both sides again. If the template changed, select its current version and create a new design.

Input Schema

TableJSON 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.
`designToken`	Yes

Output Schema

TableJSON 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.5/5.0

Behavior5/5

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

The description discloses several behavioral traits beyond annotations: the design is immutable, prior approval does not carry over to the new revision, and if the template changed, the user must select its current version and create a new design. These details add significant value and align with the idempotentHint and non-destructive annotations without contradiction.

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 somewhat long but every sentence carries weight: it covers purpose, field completeness, requestId behavior, output, approval caveat, and template change handling. It is front-loaded with the core purpose and does not include redundant filler, making it efficient for its depth.

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 tool with five parameters and nested objects, the description addresses the key operational aspects: immutability, complete field set, idempotent requestId handling, approval nuances, and template changes. The output schema exists, so return details are covered. Minor omissions like error messages beyond missing fields are already in the schema, so the description is sufficiently complete.

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?

The schema already provides thorough descriptions for parameters (80% coverage), and the description adds usage context for fields, logoUrl, and requestId, clarifying the completeness requirement and idempotency behavior. It does not introduce new parameter meanings but reinforces the schema's guidance, making it helpful.

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 clearly states the verb 'Create' and the resource 'a new immutable design from an authorized prior design', making it distinct from the sibling create_business_card_design (which likely starts from scratch) and refresh_design_proof. It emphasizes the revision nature and the immutable output, leaving no ambiguity about its function.

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?

It gives explicit instructions on how to use the tool: supply the complete field set, use a new requestId for edits and the same for retries, and handle template changes. It does not name sibling alternatives directly, but the context strongly implies when to use this versus creating a new design, so the guidance is clear though not exhaustive.

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?