Postlyra.app — Telegram posts from AI chats

Get Postlyra usage guide

get_postlyra_guide

Read-onlyIdempotent

Use this when onboarding, resolving publication modes or recovering from errors; call first for onboarding, publication modes in AI chat/browser/Mini App, connecting channels/groups or error recovery. Defaults to a short quickstart; choose topic and level=workflows for steps or reference for examples. Explains IDs, revisions, media, buttons, consent and Free attribution. Public help only: reads no user data and never sends. Use get_formatting_capabilities for full RichDocument syntax.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_postlyra_guide"
  }
}

Input Schema

Name	Required	Description	Default
`level`	No	Guide detail: quickstart for a summary, workflows for steps, reference for full examples.	quickstart
`topic`	No	Help topic to return; all returns the complete guide topic set.	all
`locale`	No	Guide language, en or ru; defaults to en.	en

Output Schema

Name	Required	Description	Default
`level`	Yes
`topic`	Yes
`locale`	Yes
`message`	Yes
`version`	Yes
`sections`	Yes
`nextAction`	Yes
`userSummary`	Yes
`betaDiagnostics`	No
`cardAfterCreate`	Yes
`publishingMatrix`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 29, 2026

addedInput schema / properties / level / description

Added value: +"Guide detail: quickstart for a summary, workflows for steps, reference for full examples."

addedInput schema / properties / locale / description

Added value: +"Guide language, en or ru; defaults to en."

addedInput schema / properties / topic / description

Added value: +"Help topic to return; all returns the complete guide topic set."

AddedOct 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: it is public help only, reads no user data, and never sends. It does not need to explain return values because an output schema exists.

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 use case is front-loaded and every sentence contributes onboarding conditions, defaults, scope, safety, or the sibling alternative. It is dense but not padded; the long first sentence is slightly run-on but still readable.

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?

With annotations covering safety, a rich input schema, and an output schema, the description supplies the remaining decision context: when to call it first, how to choose detail level, what topics it explains, and which sibling handles syntax. Nothing essential for correct selection or invocation is missing.

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 all three enums are documented, including what quickstart/workflows/reference mean and what topic/locale control. The description restates the default and level choice but adds little beyond the schema, and it does not clarify topic or locale semantics further. A baseline 3 is appropriate when the schema already carries parameter meaning.

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 uses a specific verb-resource framing ('usage guide') and immediately scopes it to onboarding, publication modes, connections, and error recovery. It clearly distinguishes this help tool from the sibling get_formatting_capabilities, which is named for syntax coverage.

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 states when to call this first ('onboarding, publication modes... connecting channels/groups or error recovery') and names the alternative for a distinct need ('Use get_formatting_capabilities for full RichDocument syntax'). The level choice is also tied to usage conditions: workflows for steps, reference for examples.

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.