thanks.io

Update Image Template

update-image-template

Destructive

Update one of the user's own image templates: rename it, replace a static design with a new image_url, or point a dynamic template at a new dynamic_image_url (its stored preview is re-rendered). The mailer type cannot be changed — create a new template with create-image-template instead. Shared system designs cannot be updated. A new image replaces a ThanksAI Studio design or a tracked QR code the template carried: it prints exactly as given, and any warnings say when tracking was dropped, so tell the user. When the new image prints a QR code thanks.io won't track, the result carries qr_code and a next_step saying what to ask the user.

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": {
      "image_template_id": "<image_template_id>"
    },
    "name": "update-image-template"
  }
}

Input Schema

Name	Required	Description
`name`	No	A new name for the template.
`image_url`	No	Replacement design for a static template. Publicly reachable JPG or PNG URL for a static front design. The image is downloaded, cropped to the product's print dimensions and stored on thanks.io, so it keeps working if the original URL goes away. Provide exactly one of image_url or dynamic_image_url.
`dynamic_image_url`	No	Replacement design for a dynamic template; the stored preview is re-rendered. A thanks.io image-builder URL (…/api/v2/build/image-template?id=<1-20>&background_url=…&header=…) containing ~TAG~ personalization variables such as ~FIRST_NAME~, ~CUSTOM1~ or ~STREET_VIEW~. Each mailer is rendered per recipient at send time; a flattened sample preview is stored now. Provide exactly one of image_url or dynamic_image_url.
`image_template_id`	Yes	The id of one of the user's own templates, from list-image-templates. Shared system designs cannot be updated.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say destructiveHint=true; the description adds what is actually lost (a ThanksAI Studio design or tracked QR code is replaced, tracking may be dropped), that warnings surface this, and that the result carries qr_code plus a next_step instructing the agent to tell the user. That is exactly the context annotations cannot convey.

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?

Front-loaded with the action and its three modes, then prerequisites, then consequences. Slightly dense in the final sentence but nearly every clause carries actionable information.

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?

No output schema exists, yet the description still tells the agent what the response contains (warnings, qr_code, next_step) and how to act on it. Combined with the mutation risks and exclusions, an agent has everything needed to call it and handle the result.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents each parameter, including the 'exactly one of image_url or dynamic_image_url' rule. The description reinforces the mutual exclusivity and the preview re-render behavior but adds little parameter-level meaning beyond the schema, so baseline 3 applies.

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?

Opening clause states a specific verb and resource ('Update one of the user's own image templates') and enumerates the three update modes (rename, replace static design, repoint dynamic design). It explicitly differentiates from the sibling create-image-template and rules out shared system designs, so 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternative path explicitly ('The mailer type cannot be changed — create a new template with create-image-template instead') and adds a hard exclusion ('Shared system designs cannot be updated'). Both the when-not and the redirect target are stated outright.

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

All thanks.io 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?