Skip to main content
Glama

InkFE Print

by com.inkfe
OverviewDiscussionsAdmin

Refresh a saved design proof

refresh_design_proof
Read-onlyIdempotent

Refresh expired front/back proof links and return both saved images for the same immutable design. Requires the original guest/integration or verified owner. Never rerenders, extends design expiry, or grants approval. Missing or expired design state requires a new design and review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guestTokenNoPrivate 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.
designTokenYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
proofYesImmutable proof identity used by approval.
saveUrlNoPrivate browser link to save the design to an InkFE account.
designIdYes
nextStepYes
previewsYesFront and back proof images; also attached as image content.
warningsYesFitting adjustments to show the buyer with the proofs.
expiresAtYesWhen the designToken expires.
revisionIdYes
templateIdYes
designTokenYesPrivate token for this immutable design; keep in the conversation.
accountOwnedNoPresent when a verified customer owns the design.
draftRetentionNoPresent for guest drafts: how long an unsaved draft is kept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already signal readOnly, idempotent, and non-destructive, and the description adds meaningful behavioral context: it never rerenders, never extends design expiry, never grants approval, and requires ownership. This goes well beyond the structured hints and aligns with them.

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 tight sentences front-load the purpose, then add exclusions and prerequisites. Every sentence earns its place with no redundant restatement of the title or schema.

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 rich annotations and an output schema, the description covers purpose, exclusions, and access prerequisites well. The main remaining gap is that the required designToken is not semantically explained in either the schema or the description.

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

Parameters2/5

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

The schema thoroughly documents guestToken, but the required designToken has no property description. With only 50% schema coverage, the description should compensate, yet it only refers obliquely to 'the same immutable design' without explaining where designToken comes from or how it should be obtained.

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?

States a specific verb and resource: refresh expired front/back proof links and return both saved images for the same immutable design. It also explicitly disambiguates from approve_design_proof and revise_business_card_design by declaring what the tool never does.

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?

Provides clear eligibility requirements (original guest/integration or verified owner) and explicit when-not-to-use guidance for missing or expired design states. It stops short of naming the exact sibling tool to use instead, though 'new design and review' and the sibling list make the alternative clear.

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

All InkFE Print toolsInspect
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