Ranla

List templates

list_templates

Read-only

List email templates.

Input Schema

Name	Required	Description
`limit`	No	Page size (1–100)
`cursor`	No	Opaque cursor for the next page
`status`	No	Only drafts or only published templates

Output Schema

Name	Required	Description
`data`	Yes	Email templates
`has_more`	No	True when another page follows
`next_cursor`	No	Pass as cursor for the next page; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / status / description

Added value: +"Only drafts or only published templates"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Email templates",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "description": "True when another page follows",
+      "type": "boolean"
+    },
+    "next_cursor": {
+      "description": "Pass as cursor for the next page; null on the last page",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

C2.7/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, so the safety profile is covered. The description adds nothing further — no pagination behavior, no mention that the cursor drives paging, and no note on default ordering or result size.

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 short, front-loaded sentence with no padding or wasted words. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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

Completeness3/5

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

Output schema exists, so return values need no explanation, and annotations plus the schema cover safety and parameters. Still missing is positioning against the many sibling list/get tools, which an agent needs to choose correctly.

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%, with limit, cursor, and status fully documented and an enum on status. The description adds no meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource ('List email templates'), so an agent knows it enumerates templates rather than fetching one. However, it is essentially a restatement of the name/title and adds only the word 'email', with no differentiation from siblings like get_template, list_emails, or create_template.

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 versus get_template (single template) or list_emails, and no mention of the filtering behavior implied by the status enum. The agent must infer usage entirely from the tool name.

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?