Skip to main content
Glama

Kalpana Batch

by one.kalpana
OverviewDiscussionsAdmin

Edit one pending job

update_job
DestructiveIdempotent

Changes one pending job that has no output yet, in any batch, including batches that are no longer drafts. The given fields replace their previous values and the rest stay, so repeating the same request gives the same result. Switching outputFormat to mp4, gif, webm or mov makes it a video job, which costs credits by its length and size when it renders. Failed, processing and rendered jobs are rejected; a failed job in a draft can still change through update_batch. Nothing renders until run_batch. For several jobs at once, or to add and remove jobs, use update_batch. Needs templates:read and batches:create.

Input Schema

NameRequiredDescriptionDefault
rowYesOnly the layers to change, keyed and valued as create_batch rows are
jobIdYesPending job ID from get_batch_jobs
outputFormatNoNew output format; omit to keep the job's format. mp4, gif, webm or mov makes it a video, which needs an animated template and costs more credits.

Output Schema

NameRequiredDescriptionDefault
idYes
statusYespending waits for run_batch, processing is rendering, success has rendered, failed has a render error, cancelled was stopped by cancel_batch or cancel_job (final, not charged)
batchIdYes
creditCostYesCredits run_batch spends on this job
outputKindYesimage for still renders (png, jpeg, webp, pdf); video for mp4, gif, webm or mov
outputFormatYesFile format the job renders to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / jobId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • changedInput schema / properties / row / additionalProperties / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "description": "A text layer's text, with <s1>...</s1> tags for runs when it has several styles; or an image layer's asset id or file name",
-        "type": "string"
-      },
-      {
-        "additionalProperties": true,
-        "description": "A text layer's text and visibility",
-        "properties": {
-          "text": {
-            "description": "The layer's new text, tagged like a string value",
-            "type": "string"
-          },
-          "visible": {
-            "description": "false hides the layer; layout closes the gap",
-            "type": "boolean"
-          }
-        },
-        "type": "object"
-      },
-      {
-        "additionalProperties": true,
-        "description": "An image layer's image and framing",
-        "properties": {
-          "asset": {
-            "description": "An asset id (search_assets, upload_images), the image's file name, or a designer image key. Omit to keep the template's image and only re-frame it.",
-            "type": "string"
-          },
-          "fit": {
-            "description": "cover fills the slot and crops (default), contain shows the whole image, stretch distorts to the slot. The designer's names work too: fill is cover, fit is contain",
-            "enum": [
-              "cover",
-              "contain",
-              "stretch",
-              "fill",
-              "fit"
-            ],
-            "type": "string"
-          },
-          "panX": {
-            "description": "Moves the image by this fraction of the slot width; positive = right",
-            "maximum": 1,
-            "minimum": -1,
-            "type": "number"
-          },
-          "panY": {
-            "description": "Moves the image by this fraction of the slot height; positive = down",
-            "maximum": 1,
-            "minimum": -1,
-            "type": "number"
-          },
-          "visible": {
-            "description": "false hides the layer",
-            "type": "boolean"
-          },
-          "zoom": {
-            "description": "Zoom about the slot centre; 1 = none",
-            "maximum": 4,
-            "minimum": 0.2,
-            "type": "number"
-          }
-        },
-        "type": "object"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "description": "A text layer's text, with <s1>...</s1> tags for runs when it has several styles; or an image layer's asset id or file name",
+        "type": "string"
+      },
+      {
+        "additionalProperties": {},
+        "description": "A text layer's text and visibility",
+        "properties": {
+          "text": {
+            "description": "The layer's new text, tagged like a string value",
+            "type": "string"
+          },
+          "visible": {
+            "description": "false hides the layer; layout closes the gap",
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      {
+        "additionalProperties": {},
+        "description": "An image layer's image and framing",
+        "properties": {
+          "asset": {
+            "description": "An asset id (search_assets, upload_images), the image's file name, or a designer image key. Omit to keep the template's image and only re-frame it.",
+            "type": "string"
+          },
+          "fit": {
+            "description": "cover fills the slot and crops (default), contain shows the whole image, stretch distorts to the slot. The designer's names work too: fill is cover, fit is contain",
+            "enum": [
+              "cover",
+              "contain",
+              "stretch",
+              "fill",
+              "fit"
+            ],
+            "type": "string"
+          },
+          "panX": {
+            "description": "Moves the image by this fraction of the slot width; positive = right",
+            "maximum": 1,
+            "minimum": -1,
+            "type": "number"
+          },
+          "panY": {
+            "description": "Moves the image by this fraction of the slot height; positive = down",
+            "maximum": 1,
+            "minimum": -1,
+            "type": "number"
+          },
+          "visible": {
+            "description": "false hides the layer",
+            "type": "boolean"
+          },
+          "zoom": {
+            "description": "Zoom about the slot centre; 1 = none",
+            "maximum": 4,
+            "minimum": 0.2,
+            "type": "number"
+          }
+        },
+        "type": "object"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / row / propertyNames
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / batchId / anyOf
      Previous value: -[
-  {
-    "format": "uuid",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "uuid",
+    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / properties / creditCost / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that unmentioned fields are preserved (merge semantics), that repeating a request is a no-op, that switching to a video format changes credit cost by length and size, that rendering is deferred to run_batch, and which scopes are required (templates:read, batches:create). Annotations only give the coarse destructive/idempotent hints; the description supplies the operational consequences.

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 scope constraint, then rejection rules, alternatives, and prerequisites in descending order of importance. Dense throughout with no filler, though the rejection/alternative sentence packs two distinct ideas together.

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?

For a destructive, nested-parameter mutation with an output schema present, the description covers everything an agent needs: eligibility of the target, merge behavior, cost implications, deferred rendering, authorization scopes, and the sibling to use for other cases. Return values are correctly left to the output schema.

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?

Schema coverage is 100%, so baseline is 3. The description adds genuine meaning on top: it clarifies the merge semantics of row (given fields replace, the rest stay) and explains the behavioral consequence of outputFormat switching to a video format, which the schema only hints at.

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 ('Changes one pending job that has no output yet, in any batch') with explicit scope, and immediately separates it from update_batch for multi-job edits. An agent can tell it apart from cancel_job and update_batch 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?

Names the conditions for use and non-use explicitly: pending only, rejected for failed/processing/rendered, failed-in-draft goes through update_batch, several jobs go through update_batch, and nothing renders until run_batch. Alternatives are named with the selector condition for each.

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

All Kalpana Batch 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