Ranla

Publish template

publish_template

Publish a template, snapshotting an immutable version for sends.

Input Schema

Name	Required	Description
`id`	No	Template id
`alias`	No	Template alias (alternative to id)
`label`	No	Optional name for this version in the template history

Output Schema

Name	Required	Description	Default
`template`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / alias / description

Added value: +"Template alias (alternative to id)"

addedInput schema / properties / id / description
```
Added value: +"Template id"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "template": {
+      "properties": {
+        "alias": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "category": {
+          "description": "transactional, product, or newsletter",
+          "type": "string"
+        },
+        "created_at": {
+          "description": "ISO 8601",
+          "type": "string"
+        },
+        "design": {
+          "description": "Block design, for blocks templates",
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "format": {
+          "description": "html or blocks",
+          "type": "string"
+        },
+        "html": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Template id",
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "preheader": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "published_at": {
+          "description": "ISO 8601",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "published_version_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "draft or published",
+          "type": "string"
+        },
+        "subject": {
+          "description": "Default subject; empty for a layout-only template",
+          "type": "string"
+        },
+        "text": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "unsubscribe_enabled": {
+          "type": "boolean"
+        },
+        "updated_at": {
+          "description": "ISO 8601",
+          "type": "string"
+        },
+        "variables": {
+          "items": {
+            "type": "string"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "warnings": {
+          "description": "Content problems found in the template",
+          "items": {
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "detail": {
+                "type": "string"
+              },
+              "message": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "id"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "template"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-destructive, closed-world write. The description adds a crucial behavioral fact: publishing creates an immutable snapshot version, which informs the agent about versioning side effects. It does not cover auth, rate limits, or what happens to previous versions, but it meaningfully extends the annotation coverage.

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?

Single sentence, front-loaded with the action and its key effect. No wasted words.

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

Completeness4/5

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

With an output schema present and annotations covering safety, the description supplies the essential purpose and the immutability consequence. It could clarify the id vs alias requirement (both optional in schema) or label usage, but the schema descriptions likely suffice for invocation.

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%, so parameter meanings are fully documented in the schema. The description adds no additional semantics for id, alias, or label. 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?

States a specific verb 'publish' and resource 'template', plus the key effect: 'snapshotting an immutable version for sends'. This distinguishes it from create_template (creation) and get_template (retrieval) without needing 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 Guidelines3/5

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

No explicit when-to-use or alternatives are given. The phrase 'for sends' implies the purpose (making a template sendable), but an agent must infer that this is the step after create_template and before send_email. No exclusions or prerequisites are stated.

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

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