streetshirts

Move text or artwork

move_element

Destructive

Move the target element within its print area. Preserve other elements and areas. Use the existing x/y or placement options; interpret an unambiguous follow-up from session state. Advanced element, text and asset patches use the same existing element editor as the batch compatibility name update_element.

Input Schema

Name	Required	Description
`options`	No	Existing arguments; advanced fields/aliases remain accepted. Supplied design patches can overwrite session content; preview/rendering can fetch public image URLs in those designs. Catalogue/session results include the full designArgumentSchema.
`subject`	Yes	The exact subject returned by start_design_session.
`requestId`	Yes	Generate a UUID for a new action. Reuse it only for retrying/polling that same action and payload. A new user edit needs a new UUID.
`sessionToken`	Yes	The private expiring capability returned by start_design_session. Do not publish it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026

addedInput schema / properties / options / properties / asset

Added value: +{
+  "description": "Preserve the complete uploaded asset object returned by the tool."
+}

addedInput schema / properties / options / properties / element

Added value: +{
+  "additionalProperties": true,
+  "description": "Existing AgenticDesignToolRequest.element patch for the selected element, including text/style, image source and placement fields. Preserve unrelated returned element fields.",
+  "type": "object"
+}

addedInput schema / properties / options / properties / text

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "additionalProperties": true,
+      "properties": {
+        "align": {
+          "enum": [
+            "left",
+            "center",
+            "right"
+          ],
+          "type": "string"
+        },
+        "coordinateSpace": {
+          "enum": [
+            "stage",
+            "print_area"
+          ],
+          "type": "string"
+        },
+        "fill": {
+          "type": "string"
+        },
+        "fontFamily": {
+          "description": "Use current designOptions fonts.",
+          "type": "string"
+        },
+        "fontSize": {
+          "type": "number"
+        },
+        "height": {
+          "type": "number"
+        },
+        "rotation": {
+          "type": "number"
+        },
+        "text": {
+          "type": "string"
+        },
+        "width": {
+          "type": "number"
+        },
+        "x": {
+          "type": "number"
+        },
+        "y": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  ],
+  "description": "Text string or object: text, fontFamily, fontSize, fill, align, x, y, width, coordinateSpace."
+}

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / options / description

Previous value: -"Existing arguments; advanced fields/aliases remain accepted. Catalogue/session results include the full designArgumentSchema."New value: +"Existing arguments; advanced fields/aliases remain accepted. Supplied design patches can overwrite session content; preview/rendering can fetch public image URLs in those designs. Catalogue/session results include the full designArgumentSchema."

First observedOct 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value with "Preserve other elements and areas," scoping what the mutation does not touch, but it never says what is replaced (the element's prior position/size) or how the session state is affected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in the first sentence, which is good. The trailing sentence about "batch compatibility name update_element" is opaque jargon and "Advanced element, text and asset patches" reads as filler that dilutes an otherwise short definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive mutation with a large nested options object and no output schema, and the description does not cover the response shape or recovery path. It does at least tie the element patch to the existing editor and the required session/subject/idempotency fields are documented in the schema, so it is adequate but thin for the complexity.

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% including a detailed placement description, so the schema carries the load. The description only points at "x/y or placement options" and a follow-up instruction, adding no format, unit, or coordinate-space detail beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Move the target element within its print area" gives a specific verb and resource, and the "within its print area" scope implicitly separates it from move_to_print_area. It never names a sibling explicitly, so an agent must infer the boundary from the phrasing alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

"Use the existing x/y or placement options" and "interpret an unambiguous follow-up from session state" give invocation hints, but nothing says when to prefer this over align_element, resize_element, rotate_element, or move_to_print_area. Usage is implied rather than routed.

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

All streetshirts 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?