Postlyra

Update a Postlyra post draft

update_post_draft

Destructive

Use this when editing a draft. Read preview_post and get_formatting_capabilities. Send the complete edited richDocument, preserving untouched content and media; text replaces layout. Bind imported file slots as media.src. Returns JPEG and enables a public preview link. Display the image in the FINAL answer via native attachment or display.imageMarkdown. Inspect preview_post. May fetch external image URLs during import or screenshot rendering. Never publishes.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	No	Replaces the existing layout using the simple text parser. Prefer richDocument to preserve formatting and media.
`draftId`	Yes
`channelId`	No	Optional owner-bound Postlyra channel id or exact title returned by list_channels.
`mediaFile1`	No	Actual attached or generated image file, up to 10 MiB: JPEG, PNG, GIF or WebP. Pass the file through the client upload mechanism; the server receives download_url and file_id. mime_type and file_name may be omitted. In the same richDocument call, use this slot name as media.src for exact placement.
`mediaFile2`	No	Actual attached or generated image file, up to 10 MiB: JPEG, PNG, GIF or WebP. Pass the file through the client upload mechanism; the server receives download_url and file_id. mime_type and file_name may be omitted. In the same richDocument call, use this slot name as media.src for exact placement.
`mediaFile3`	No	Actual attached or generated image file, up to 10 MiB: JPEG, PNG, GIF or WebP. Pass the file through the client upload mechanism; the server receives download_url and file_id. mime_type and file_name may be omitted. In the same richDocument call, use this slot name as media.src for exact placement.
`mediaFile4`	No	Actual attached or generated image file, up to 10 MiB: JPEG, PNG, GIF or WebP. Pass the file through the client upload mechanism; the server receives download_url and file_id. mime_type and file_name may be omitted. In the same richDocument call, use this slot name as media.src for exact placement.
`mediaFile5`	No	Actual attached or generated image file, up to 10 MiB: JPEG, PNG, GIF or WebP. Pass the file through the client upload mechanism; the server receives download_url and file_id. mime_type and file_name may be omitted. In the same richDocument call, use this slot name as media.src for exact placement.
`mediaFile6`	No	Actual attached or generated image file, up to 10 MiB: JPEG, PNG, GIF or WebP. Pass the file through the client upload mechanism; the server receives download_url and file_id. mime_type and file_name may be omitted. In the same richDocument call, use this slot name as media.src for exact placement.
`mediaFiles`	No	Alternative file array for clients supporting file arrays. Prefer mediaFile1..mediaFile6 otherwise. At most 6 files total across slots and array; use mediaFiles[0] etc. as richDocument src bindings.
`references`	No
`templateId`	No
`instructions`	No	Limited hints only: shorter, title, quote, CTA. For rewriting, restyling or exact placement supply the complete richDocument; this field does not run an AI editor.
`richDocument`	No	Complete replacement RichDocument: {version:1, blocks:[...]}. Start from preview_post.documentJson and preserve untouched content and stored media URLs. Read get_formatting_capabilities for syntax and file-slot bindings.
`appendCallToAction`	No

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`text`	No
`title`	No
`locale`	No
`status`	No
`display`	No
`draftId`	Yes
`message`	Yes
`richHtml`	No
`updatedAt`	No
`previewUrl`	Yes
`screenshot`	No
`documentJson`	No
`inlineButtons`	No
`screenshotUrl`	No	JPEG screenshot of the saved Telegram preview; null if rendering is temporarily unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

While annotations already mark the call as destructive and non-read-only, the description adds meaningful side effects: it replaces layout with text, may fetch external image URLs, returns a JPEG, and enables a public preview link. No statement contradicts the 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 front-loaded with usage and prerequisites and contains useful side-effect/display notes. It is slightly redundant ('Read preview_post' appears again as 'Inspect preview_post'), but overall every sentence contributes to correct invocation.

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 tool with 15 params and nested objects, the description provides the essential workflow: read preview, get formatting capabilities, submit a complete richDocument, display the resulting image, and avoid publishing. An output schema exists, so not detailing every return field is acceptable; a small gap is the lack of explicit guidance for non-draft workflows.

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 73% and the schema already documents richDocument, text, and mediaFile slot semantics in detail. The description condenses these ('Send the complete edited richDocument...', 'Bind imported file slots as media.src') but adds little information beyond the schema, and it does not clarify undocumented params like templateId or appendCallToAction.

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 opens with 'Use this when editing a draft' and repeatedly frames the action as updating a Postlyra draft, ending with 'Never publishes.' It clearly identifies the target resource and verb, but it never explicitly contrasts with the sibling update_post tool, so it does not fully disambiguate from all alternatives.

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?

The first sentence gives an explicit use condition ('when editing a draft') and the description includes hard exclusions ('Never publishes') and required precursor reads ('Read preview_post and get_formatting_capabilities'). It does not name alternative tools for non-draft publishing scenarios, stopping just short of the full when/when-not/alternatives guidance.

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

All Postlyra 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.