Skip to main content
Glama
Sign In
Carbone MCP

Carbone MCP

Official
by carboneio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Template Metadata

update_template_metadata
DestructiveIdempotent

Update a stored template version's name, comment, category, tags, deployment time, expiry, or parent template so Carbone renders and manages the correct version.

Instructions

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

NameRequiredDescriptionDefault
idNoDEPRECATED: the 1.6.0 name of moveToTemplateId, kept so existing callers keep working. Use moveToTemplateId; passing both with different values is rejected.
nameNoNew display name, max 200 characters.
tagsNoNew 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).
commentNoNew free-text comment, max 200 characters.
categoryNoNew category, max 200 characters.
expireAtNoSchedule 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.
deployedAtNoUnix 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.
templateIdYesTemplate 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.
moveToTemplateIdNoCAUTION, 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

NameRequiredDescriptionDefault
idNoTemplate ID the version now belongs to (returned when moveToTemplateId was used).
nameNoName, returned if updated.
tagsNoTags, returned if updated.
commentNoComment, returned if updated.
categoryNoCategory, returned if updated.
expireAtNoDeletion timestamp (0 = never expires), returned if updated.
versionIdYesVersion ID of the patched version.
deployedAtNoDeployment timestamp, returned if updated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.4
    • addedInput schema / properties / tags / items / maxLength
      Added value: +96
    • addedInput schema / properties / tags / items / minLength
      Added value: +1
    • addedInput schema / properties / tags / maxItems
      Added value: +100
  2. Changed16 schema fields changedv2.0.0
    • 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"
+}
  3. Changed1 schema field changedv1.6.0
    • 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"
+}
  4. First observedv1.1.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this as destructive, non-read-only, and idempotent, but the description adds substantial context: expireAt causes 404 and eventual file purge, deployedAt has a special NOW value and cannot move backward, and moveToTemplateId is a structural change with fallback behavior on the source template. These details go well beyond the annotations.

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 the core action and then layers on the important behavioral rules without filler. Every sentence carries actionable information for a 9-parameter mutation tool.

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 output schema exists, so the return values needn't be fully explained, but the description still notes that the patched versionId and updated fields are echoed back. Combined with annotations and full schema coverage, an agent has everything needed to invoke the tool correctly.

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?

With 100% schema coverage, the schema already documents each parameter in depth, so the baseline is 3. The description adds a useful consolidated semantic layer—grouping the fields and clarifying the Template ID vs Version ID patching rule—but much of this overlaps the schema, keeping it below a full 5.

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 states a specific verb and resource ('Update the metadata of ONE stored template version') and enumerates the updatable fields, so an agent can immediately tell what the tool touches. It also distinguishes itself from delete_template and separates Template ID vs Version ID semantics.

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 gives explicit when-to-use rules: Template ID patches only the deployed version, Version ID patches the exact version, and deployedAt selects the version used for rendering by Template ID. It also names delete_template for immediate deletion and cautions that moveToTemplateId should be used only when the user asks to move a version.

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

Deploy Server

Other Tools