Carbone MCP

Update Template Metadata

update_template_metadata

Idempotent

Update the metadata of ONE stored template version: name, comment, category, tags, deployment (deployedAt), scheduled deletion (expireAt), or the Template ID it belongs to (moveToTemplateId). With a Template ID, Carbone patches its currently deployed version only; with a Version ID, that exact version. Use deployedAt to choose the version used when rendering by Template ID. Returns the patched versionId and the updated fields, as echoed back by Carbone. To delete a template now, use delete_template.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	DEPRECATED: the 1.6.0 name of moveToTemplateId, kept so existing callers keep working. Use moveToTemplateId; passing both with different values is rejected.
`name`	No	New display name, max 200 characters.
`tags`	No	New list of tags, replacing the existing ones. Duplicates are removed and the list is sorted; the whole list is limited to 100 characters (about 8 tags of 9 characters).
`comment`	No	New free-text comment, max 200 characters.
`category`	No	New category, max 200 characters.
`expireAt`	No	Schedule deletion of the patched version at a UTC Unix timestamp (seconds). After that time it is no longer listed, downloadable or renderable (404), and the file is purged after the retention delay. Send 0 to cancel a scheduled deletion (permanent again); omit to leave it unchanged. To delete now, use delete_template.
`deployedAt`	No	Unix timestamp (seconds) to set as the deployment time for this version. Carbone picks the version with the most recent deployedAt when rendering by Template ID. Use 42000000000 to deploy immediately (special "NOW" value). Future values are not allowed, and the deployed version's deployedAt cannot move back in time.
`templateId`	Yes	Template ID (64-bit) or Version ID (SHA-256) of the version to update. A Template ID patches only its currently deployed version (not every version). A Version ID patches that exact version.
`moveToTemplateId`	No	CAUTION, structural change: moves the patched version to this other Template ID (64-bit; a Version ID is rejected). It is NOT the template to patch (that is templateId). Pass the version's Version ID as templateId; with a Template ID, its currently deployed version is moved and that Template ID falls back to its next most recent version (or stops resolving if none is left). Fails if the move creates a deployedAt conflict at the destination. Only use it when the user asks to move a version.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Template ID the version now belongs to (returned when moveToTemplateId was used).
`name`	No	Name, returned if updated.
`tags`	No	Tags, returned if updated.
`comment`	No	Comment, returned if updated.
`category`	No	Category, returned if updated.
`expireAt`	No	Deletion timestamp (0 = never expires), returned if updated.
`versionId`	Yes	Version ID of the patched version.
`deployedAt`	No	Deployment timestamp, returned if updated.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 14, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / category / description

Previous value: -"New category."New value: +"New category, max 200 characters."

addedInput schema / properties / category / maxLength
```
Added value: +200
```

changedInput schema / properties / comment / description

Previous value: -"New free-text comment."New value: +"New free-text comment, max 200 characters."

addedInput schema / properties / comment / maxLength
```
Added value: +200
```

changedInput schema / properties / deployedAt / description

Previous value: -"Unix timestamp (seconds) to set as the deployment time for this version. Carbone picks the version with the most recent deployedAt when rendering. Use 42000000000 to deploy immediately (special \"NOW\" value)."New value: +"Unix timestamp (seconds) to set as the deployment time for this version. Carbone picks the version with the most recent deployedAt when rendering by Template ID. Use 42000000000 to deploy immediately (special \"NOW\" value). Future values are not allowed, and the deployed version's deployedAt cannot move back in time."

changedInput schema / properties / expireAt / description

Previous value: -"Unix timestamp (seconds) at which this template will be automatically deleted. Use 42000000000 to delete immediately."New value: +"Schedule deletion of the patched version at a UTC Unix timestamp (seconds). After that time it is no longer listed, downloadable or renderable (404), and the file is purged after the retention delay. Send 0 to cancel a scheduled deletion (permanent again); omit to leave it unchanged. To delete now, use delete_template."

changedInput schema / properties / expireAt / minimum
```
Previous value: --9007199254740991New value: +0
```

changedInput schema / properties / id / description

Previous value: -"Move this version under a DIFFERENT Template ID, re-parenting it so both share a version history. Pass the destination Template ID (64-bit). Leave unset to keep the version where it is — this does not rename anything, use name for that."New value: +"DEPRECATED: the 1.6.0 name of moveToTemplateId, kept so existing callers keep working. Use moveToTemplateId; passing both with different values is rejected."

addedInput schema / properties / id / minLength
```
Added value: +1
```

addedInput schema / properties / moveToTemplateId

Added value: +{
+  "description": "CAUTION, structural change: moves the patched version to this other Template ID (64-bit; a Version ID is rejected). It is NOT the template to patch (that is templateId). Pass the version's Version ID as templateId; with a Template ID, its currently deployed version is moved and that Template ID falls back to its next most recent version (or stops resolving if none is left). Fails if the move creates a deployedAt conflict at the destination. Only use it when the user asks to move a version.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / name / description

Previous value: -"New display name."New value: +"New display name, max 200 characters."

addedInput schema / properties / name / maxLength
```
Added value: +200
```

changedInput schema / properties / tags / description

Previous value: -"New list of tags — replaces existing tags entirely."New value: +"New list of tags, replacing the existing ones. Duplicates are removed and the list is sorted; the whole list is limited to 100 characters (about 8 tags of 9 characters)."

changedInput schema / properties / templateId / description

Previous value: -"Template ID (64-bit) or Version ID (SHA-256) to update. Using a Template ID updates the metadata shared by all versions. Using a Version ID updates only that specific version."New value: +"Template ID (64-bit) or Version ID (SHA-256) of the version to update. A Template ID patches only its currently deployed version (not every version). A Version ID patches that exact version."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "category": {
+      "description": "Category, returned if updated.",
+      "type": "string"
+    },
+    "comment": {
+      "description": "Comment, returned if updated.",
+      "type": "string"
+    },
+    "deployedAt": {
+      "description": "Deployment timestamp, returned if updated.",
+      "type": "number"
+    },
+    "expireAt": {
+      "description": "Deletion timestamp (0 = never expires), returned if updated.",
+      "type": "number"
+    },
+    "id": {
+      "description": "Template ID the version now belongs to (returned when moveToTemplateId was used).",
+      "type": "string"
+    },
+    "name": {
+      "description": "Name, returned if updated.",
+      "type": "string"
+    },
+    "tags": {
+      "description": "Tags, returned if updated.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "versionId": {
+      "description": "Version ID of the patched version.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "versionId"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 19, 2026

addedInput schema / properties / id

Added value: +{
+  "description": "Move this version under a DIFFERENT Template ID, re-parenting it so both share a version history. Pass the destination Template ID (64-bit). Leave unset to keep the version where it is — this does not rename anything, use name for that.",
+  "type": "string"
+}

First observedMar 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover only the safety profile (idempotent, non-destructive), while the description adds real behavioral substance: Template ID patches only the currently deployed version, Version ID patches that exact version, moveToTemplateId is a structural move with fallback consequences, and expireAt can be cancelled with 0. It also states the return payload (patched versionId + echoed fields), which annotations do not 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?

A single dense paragraph, front-loaded with the action and the affected fields, with no filler sentences. It is somewhat long and mildly overlaps with the output schema when describing the return value, but every clause carries usable 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?

For a 9-parameter mutation tool with an output schema and safety annotations, the description supplies the missing linkage: which identifier patches which version, how deployment ordering affects rendering, and what the destructive-ish paths (expireAt, moveToTemplateId) do. Nothing an agent needs to call this correctly is absent.

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 description coverage is 100% and the per-parameter docs are extremely detailed (deployedAt NOW value, moveToTemplateId caution, expireAt semantics), so the baseline is 3. The description's parameter remarks ('Use deployedAt to choose the version used when rendering by Template ID') largely restate what the schema already documents rather than adding new syntax or format meaning.

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 opens with a specific verb+resource ('Update the metadata of ONE stored template version') and enumerates the exact mutable fields. It distinguishes its scope from siblings by routing deletion to delete_template, so an agent can separate it from delete_template and inspect_template without opening a schema.

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?

It names the alternative for deletion ('To delete a template now, use delete_template') and distinguishes the two invocation modes (Template ID vs Version ID) that determine which version gets patched. It gives clear context but no broader when-not-to-use guidance (e.g. when inspection or re-upload is preferable).

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

All Carbone MCP 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.