InkFE Print

List business card templates

list_business_card_templates

Read-onlyIdempotent

Start here to design a business card. Lists the InkFE Classic business card templates a buyer can personalise, with templateId, name, orientation (landscape or portrait), widthInches and heightInches, previewUrls for the front and back artwork, hasBack, the productHandle to purchase, and the fields the template needs. Each field has an attribute (the key to send when creating a design), a human label, the side it prints on (front, back or both), an inputType (text, multiline, url for a QR code destination, or imageUrl for a logo), whether it is required, and a sampleValue showing the placeholder text so you can judge length and tone. Show the buyer the preview images and field list, help them pick a template, then collect a value for every required field (a logo field needs a public https PNG or JPEG URL; a QR field needs the https URL the code should open). Check the productHandle with get_product and follow its artwork workflow. For a supported product, call create_business_card_design with the collected values and templateId. After preview approval and configuration selection, call get_quote, show the commercial terms and obtain confirmation. Pass designToken and quoteToken to create_checkout for a Shopify checkout URL. Takes no arguments.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`templates`	Yes

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": {
+    "templates": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "fields": {
+            "items": {
+              "additionalProperties": {},
+              "properties": {
+                "attribute": {
+                  "description": "Key to send in fields.",
+                  "type": "string"
+                },
+                "inputType": {
+                  "enum": [
+                    "text",
+                    "multiline",
+                    "url",
+                    "imageUrl"
+                  ],
+                  "type": "string"
+                },
+                "label": {
+                  "type": "string"
+                },
+                "maxLines": {
+                  "maximum": 9007199254740991,
+                  "minimum": -9007199254740991,
+                  "type": "integer"
+                },
+                "required": {
+                  "type": "boolean"
+                },
+                "sampleValue": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "side": {
+                  "enum": [
+                    "front",
+                    "back",
+                    "both"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "attribute",
+                "label",
+                "side",
+                "inputType",
+                "required",
+                "sampleValue"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "hasBack": {
+            "type": "boolean"
+          },
+          "heightInches": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "orientation": {
+            "enum": [
+              "landscape",
+              "portrait"
+            ],
+            "type": "string"
+          },
+          "previewUrls": {
+            "additionalProperties": {},
+            "properties": {
+              "back": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "front": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "front",
+              "back"
+            ],
+            "type": "object"
+          },
+          "productHandle": {
+            "description": "The product to quote and buy.",
+            "type": "string"
+          },
+          "templateId": {
+            "description": "Pass to create_business_card_design.",
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "widthInches": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "templateId",
+          "name",
+          "orientation",
+          "widthInches",
+          "heightInches",
+          "previewUrls",
+          "hasBack",
+          "fields",
+          "productHandle"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "templates"
+  ],
+  "type": "object"
+}

First observedSep 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the tool 'Takes no arguments', describes the list payload, and clarifies that no purchase is initiated at this step. It could mention pagination or data freshness, but annotations plus this description give sufficient behavioral transparency.

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?

The description is front-loaded with 'Start here', then gives return-field semantics, buyer-facing guidance, and the exact workflow sequence. Although long, every sentence carries operational value; there is no filler or repetition.

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?

The tool is a no-argument read operation, has an output schema, and has strong annotations. The description fully covers what the tool returns, how to interpret each field, and how to proceed through the sibling tools. Nothing needed to call it correctly or continue the workflow is missing.

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?

There are zero parameters, so the baseline is 4 and the schema imposes no burden. The description explicitly states 'Takes no arguments', confirming the empty schema. It also explains how the returned fields should be used, which is more than necessary for a no-argument tool.

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 uses a specific verb and resource: 'Lists the InkFE Classic business card templates a buyer can personalise'. It enumerates the key fields returned and distinguishes this as the starting point for the design workflow, clearly separating it from later mutation steps like create_business_card_design.

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?

It explicitly says 'Start here to design a business card' and then names the exact downstream tools and order: check productHandle with get_product, call create_business_card_design, use get_quote, and pass tokens to create_checkout. This gives an agent explicit when-to-use and next-step guidance rather than leaving sequencing to inference.

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?