Scribe Mail

Create a signature

create_signature

Create a signature template. Sets draft_content (the working copy) — content stays empty until you publish_signature. name is required; draft_content is a block tree (a stack root whose children are blocks) strict-validated server-side; folder_id is a folder UUID. Call get_content_schema FIRST for the block-tree schema, every enum value (incl. the non-obvious icon names like linkedin-in/facebook-f), and a complete worked example to adapt — that's how you build a full signature, social-icon row included, in one shot. An invalid tree returns 422 naming each offending field and (for enums) its allowed values. Returns the created template.

Input Schema

Name	Required	Description
`name`	Yes	Signature template name (required).
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`priority`	No	Ordering priority (lower = higher).
`folder_id`	No	UUID of the folder to file the signature under; null detaches it.
`draft_content`	No	Draft block tree (ILayoutBlock): a `stack` root whose `children` are blocks. Strict-validated server-side. Omit to leave unchanged; null to clear. Every node (block AND token) needs an `id` that is a fresh LOWERCASE uuid — any other string, including an uppercase uuid, is rejected 422. Every numeric size is in PIXELS, never a CSS multiplier: `lineHeight` is a px line box (~1.3x fontSize, e.g. fontSize 14 -> 18), so 1.3 is rejected. Call get_content_schema for the full schema, every enum value, and a worked example.
`signature_installation_activated`	No	Whether installation is activated for this template.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 28, 2026

changedInput schema / properties / draft_content / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "blockStyle": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "children": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "id": {
-              "description": "Lowercase uuid (8-4-4-4-12 hex), e.g. 6f1e8a2c-4b0d-4c8e-9f3a-2d7b5e9c1a4f. Generate a fresh one per element and keep it stable across updates so a link keeps its click-tracking identity.",
-              "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
-              "type": "string"
-            },
-            "role": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "type": {
-              "enum": [
-                "stack",
-                "text",
-                "image",
-                "icon",
-                "list",
-                "listItem",
-                "listItemLabel",
-                "socialList",
-                "socialListItem",
-                "button",
-                "divider",
-                "marketing"
-              ],
-              "type": "string"
-            },
-            "visible": {
-              "type": "boolean"
-            }
-          },
-          "required": [
-            "id",
-            "type",
-            "role",
-            "visible"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "id": {
-        "description": "Lowercase uuid (8-4-4-4-12 hex), e.g. 6f1e8a2c-4b0d-4c8e-9f3a-2d7b5e9c1a4f. Generate a fresh one per element and keep it stable across updates so a link keeps its click-tracking identity.",
-        "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
-        "type": "string"
-      },
-      "role": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "type": {
-        "const": "stack",
-        "type": "string"
-      },
-      "visible": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "id",
-      "type",
-      "role",
-      "visible",
-      "blockStyle",
-      "children"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "blockStyle": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "children": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "id": {
+              "description": "Lowercase uuid (8-4-4-4-12 hex), e.g. 6f1e8a2c-4b0d-4c8e-9f3a-2d7b5e9c1a4f. Generate a fresh one per element and keep it stable across updates so a link keeps its click-tracking identity.",
+              "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
+              "type": "string"
+            },
+            "role": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "enum": [
+                "stack",
+                "text",
+                "image",
+                "icon",
+                "list",
+                "listItem",
+                "listItemLabel",
+                "socialList",
+                "socialListItem",
+                "button",
+                "divider",
+                "marketing"
+              ],
+              "type": "string"
+            },
+            "visible": {
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "id",
+            "type",
+            "role",
+            "visible"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "id": {
+        "description": "Lowercase uuid (8-4-4-4-12 hex), e.g. 6f1e8a2c-4b0d-4c8e-9f3a-2d7b5e9c1a4f. Generate a fresh one per element and keep it stable across updates so a link keeps its click-tracking identity.",
+        "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
+        "type": "string"
+      },
+      "role": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "type": {
+        "const": "stack",
+        "type": "string"
+      },
+      "visible": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "role",
+      "visible",
+      "blockStyle",
+      "children"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / folder_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / folder_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / properties / folder_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / properties / folder_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / properties / internal_variant_uuid / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / properties / internal_variant_uuid / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / properties / last_published_at / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / properties / last_published_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / properties / priority / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / properties / priority / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / data / properties / reply_variant_uuid / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / properties / reply_variant_uuid / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write/non-idempotent profile is structured. The description nevertheless adds real value beyond that: strict server-side validation returning 422 with offending fields and allowed enum values, and the lowercase-UUID/pixel-units constraints. These are useful but framed as parameter rules rather than additional behavioral traits like permissions or side effects.

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?

Front-loads the create action and the draft-vs-published distinction, then builds prerequisites. It is dense and slightly run-on with em-dash nesting, but nearly every clause carries actionable information (state effect, schema-first pointer, 422 behavior, id/unit rules).

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?

Given 6 parameters, nested block-tree complexity, and annotations plus an output schema, the description supplies the workflow ordering, validation behavior, unit/id constraints, and return note. Nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100%, so baseline is 3, and the description still adds meaning: `name` required, `draft_content` is a strict-validated block tree, `folder_id` is a folder UUID. It goes further with unit semantics (pixels not multipliers, lineHeight example) and lowercase-UUID id stability, exceeding what the schema alone conveys.

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?

Opens with a specific verb+resource ('Create a signature template') and immediately clarifies the state effect: sets `draft_content` while `content` stays empty until publish_signature. This cleanly distinguishes it from create_first_signature, update_signature, and publish_signature siblings.

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?

Explicitly instructs to 'Call `get_content_schema` FIRST' and explains why (full schema, enum values, worked example), plus names publish_signature as the follow-on action. The when-to-use and prerequisite ordering is fully spelled out.

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

All Scribe Mail 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.