Postlyra.app — Telegram posts from AI chats

Preview a Postlyra post

preview_post

Idempotent

Use this when requesting a saved draft screenshot, public browser preview or validation warnings. Find draftId with search_post_drafts. Returns documentJson/richHtml, JPEG and enables a public preview link. Use show_post_card for an in-chat card. Follow display.instruction; check screenshot.truncated and retry unavailable screenshots without recreating the draft. May fetch external image URLs for screenshot rendering. Never publishes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`draftId`	Yes
`channelId`	No	Preview this owner-bound channel's auto-signature. Without a channel use the account default or post override.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`card`	No	Interactive card attachment and fallback instructions. attachedToThisResult means this response already supplies the card; do not automatically call show_post_card again. Host support determines actual rendering.
`text`	No
`title`	No
`locale`	No
`postId`	No
`status`	No
`display`	No
`draftId`	Yes
`message`	Yes
`revision`	No
`richHtml`	No
`warnings`	Yes
`channelId`	No
`updatedAt`	No
`previewUrl`	No
`screenshot`	No
`validation`	Yes
`mediaStatus`	No	Present only when image inputs were validated and imported into durable storage during this call. It does not describe arbitrary external document media.
`documentJson`	No
`inlineButtons`	No
`screenshotUrl`	No	JPEG screenshot of the saved Telegram preview; null if rendering is temporarily unavailable.
`telegramElements`	No
`signatureSnapshot`	No
`signatureSelection`	No
`deliveryDocumentJson`	No	Composed publication including the selected auto-signature. Edit documentJson, never copy this composition into the post body.
`deliveryInlineButtons`	No
`formattingSuggestions`	No	Optional formatting ideas. They do not affect validation, publication or user consent. The user's choice always takes priority.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / properties / card / description

Previous value: -"Interactive card availability and fallback instructions. Host UI support determines whether a card can render; preview links remain available."New value: +"Interactive card attachment and fallback instructions. attachedToThisResult means this response already supplies the card; do not automatically call show_post_card again. Host support determines actual rendering."

Changed1 schema field changedOct 14, 2026

addedOutput schema / properties / formattingSuggestions

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional formatting ideas. They do not affect validation, publication or user consent. The user's choice always takes priority.",
+  "properties": {
+    "advisory": {
+      "const": true,
+      "type": "boolean"
+    },
+    "decisionOwner": {
+      "const": "user",
+      "type": "string"
+    },
+    "instruction": {
+      "type": "string"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "blockPaths": {
+            "items": {
+              "type": "string"
+            },
+            "maxItems": 5,
+            "type": "array"
+          },
+          "code": {
+            "type": "string"
+          },
+          "message": {
+            "type": "string"
+          },
+          "recommendation": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "code",
+          "message",
+          "recommendation",
+          "blockPaths"
+        ],
+        "type": "object"
+      },
+      "maxItems": 4,
+      "type": "array"
+    }
+  },
+  "required": [
+    "advisory",
+    "decisionOwner",
+    "instruction",
+    "items"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedOct 13, 2026

addedOutput schema / properties / card

Added value: +{
+  "description": "Interactive card availability and fallback instructions. Host UI support determines whether a card can render; preview links remain available.",
+  "type": "object"
+}

addedOutput schema / properties / mediaStatus

Added value: +{
+  "description": "Present only when image inputs were validated and imported into durable storage during this call. It does not describe arbitrary external document media.",
+  "enum": [
+    "imported"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / postId

Added value: +{
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / revision

Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}

Changed8 schema fields changedOct 9, 2026

addedInput schema / properties / channelId

Added value: +{
+  "description": "Preview this owner-bound channel's auto-signature. Without a channel use the account default or post override.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / channelId

Added value: +{
+  "maxLength": 128,
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / deliveryDocumentJson

Added value: +{
+  "description": "Composed publication including the selected auto-signature. Edit documentJson, never copy this composition into the post body.",
+  "type": "object"
+}

addedOutput schema / properties / deliveryInlineButtons

Added value: +{
+  "items": {
+    "anyOf": [
+      {
+        "type": "object"
+      },
+      {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    ]
+  },
+  "type": "array"
+}

addedOutput schema / properties / inlineButtons / items / anyOf

Added value: +[
+  {
+    "type": "object"
+  },
+  {
+    "items": {
+      "type": "object"
+    },
+    "type": "array"
+  }
+]

removedOutput schema / properties / inlineButtons / items / type
```
Removed value: -"object"
```

addedOutput schema / properties / signatureSelection

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "mode": {
+      "enum": [
+        "inherit",
+        "none",
+        "custom"
+      ],
+      "type": "string"
+    },
+    "signatureId": {
+      "maxLength": 128,
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "mode"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / signatureSnapshot

Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}

First observedSep 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds significant behavioral context beyond annotations: it discloses that it may fetch external image URLs, enables a public preview link, never publishes, and gives instructions for handling truncated or unavailable screenshots. This goes well beyond the readOnlyHint=false and openWorldHint=true annotations.

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?

The description is dense but front-loaded with the core usage case. Every sentence adds useful information, though it could be slightly more structured.

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 the presence of an output schema, the description doesn't need to detail return values. It covers all necessary behavioral aspects: preview types, external image fetching, failure handling, and non-publishing nature, making it complete for an agent to invoke correctly.

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 50%, and the description compensates by telling how to find draftId via search_post_drafts. It doesn't explain channelId's purpose, which is covered in the schema description, so it adds some but not complete value.

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?

The description clearly states the tool's purpose: requesting a saved draft screenshot, public browser preview or validation warnings. It specifies what it returns (documentJson/richHtml, JPEG) and distinguishes itself from show_post_card by name.

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?

It explicitly says when to use this tool ('Use this when requesting a saved draft screenshot...') and provides a direct alternative for in-chat cards ('Use show_post_card for an in-chat card'). It also instructs how to find draftId and handle screenshot failures.

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

All Postlyra.app — Telegram posts from AI chats 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.