Ranla

Get template

get_template

Read-only

Get a template by id or alias.

Input Schema

Name	Required	Description	Default
`id`	No	Template id
`alias`	No	Published alias (alternative to id)

Output Schema

Name	Required	Description	Default
`template`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

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

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds no behavioral context beyond that — nothing about failure modes when the id/alias is unknown, or about draft vs published template behavior.

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?

A single eight-word sentence, front-loaded with the verb and resource. Every word earns its place; nothing is padded or redundant.

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?

For a simple single-record read with an output schema, full parameter documentation, and annotations covering safety, the definition is nearly complete. The only gap is the absence of any routing hint toward list_templates or note on alias resolution, which is minor here.

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 both parameters are documented in the schema, including that alias is an alternative to id. The description's 'by id or alias' merely restates that, adding no format or precedence detail. Baseline 3 is appropriate.

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?

The description states a specific verb ('Get') and resource ('template') and clarifies the lookup key ('by id or alias'). This distinguishes it from list_templates and create_template, though it does not explicitly name those siblings. Clear and unambiguous, but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus list_templates, nor on prerequisites such as whether the alias must be published. The agent must infer usage entirely from the name and schema.

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?