Ranla

Create template

create_template

Create a draft email template (html or blocks format). Publish it before sending with it.

Input Schema

Name	Required	Description
`html`	No	HTML body (html format). Variables like {{name}} are allowed
`name`	Yes	Template name shown in the dashboard
`text`	No	Plain-text body
`alias`	No	Stable name to send with (template_alias), e.g. password-reset
`format`	No	html for a raw HTML body, or blocks for the dashboard block editor
`subject`	No	Default subject line. Variables like {{name}} are allowed

Output Schema

Name	Required	Description	Default
`template`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 14, 2026

addedInput schema / properties / alias / description

Added value: +"Stable name to send with (template_alias), e.g. password-reset"

addedInput schema / properties / format / description

Added value: +"html for a raw HTML body, or blocks for the dashboard block editor"

addedInput schema / properties / html / description

Added value: +"HTML body (html format). Variables like {{name}} are allowed"

addedInput schema / properties / name / description

Added value: +"Template name shown in the dashboard"

addedInput schema / properties / subject / description

Added value: +"Default subject line. Variables like {{name}} are allowed"

addedInput schema / properties / text / description
```
Added value: +"Plain-text body"
```

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 readOnlyHint=false and destructiveHint=false, so the write-but-non-destructive profile is already covered. The description adds genuinely useful behavioral context beyond that: the created template is a draft, not immediately sendable, and must be published first. It does not mention duplicate-name/alias handling or permissions, but the key state transition is disclosed.

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?

Two short sentences, zero padding, with the core action (create draft) and the format scope front-loaded before the publish prerequisite. Every sentence earns its place.

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?

An output schema exists, so return values need no explanation here, and annotations cover the safety profile. The description supplies the essential lifecycle fact (draft must be published before sending), leaving only minor items like duplicate alias behavior unaddressed.

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 schema already documents all six parameters including the html/blocks enum. The description's 'html or blocks format' merely echoes the format parameter, adding no syntax, default, or validation meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource (create an email template) and narrows the artifact to a 'draft' in html or blocks format, which separates it from publish_template, get_template, and list_templates. It stops short of naming a sibling explicitly, so it is clear but not fully differentiated.

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?

'Publish it before sending with it' gives a concrete follow-up workflow step and implicitly frames this as the first stage of a two-step create/publish flow, distinguishing it from publish_template. There is no explicit when-not or alternative-selection guidance, but the context is clear.

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?