Postlyra.app — Telegram posts from AI chats

Save a personal template

create_template

Use when the author asks to save a reusable post layout. Supply a name and RichDocument. Creates an owner-only template without publishing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "documentJson": "<documentJson>"
    },
    "name": "create_template"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name for the personal template, e.g. Weekly recap.
`locale`	No	Language code, e.g. en or ru.
`category`	No	Template category label, e.g. news.
`description`	No	Short description of the template purpose.
`documentJson`	Yes	Complete RichDocument working layout; see get_formatting_capabilities for syntax and preserve untouched blocks when replacing.

Output Schema

Name	Required	Description	Default
`data`	Yes
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 29, 2026

addedInput schema / properties / category / description
```
Added value: +"Template category label, e.g. news."
```

addedInput schema / properties / description / description

Added value: +"Short description of the template purpose."

addedInput schema / properties / documentJson / description

Added value: +"Complete RichDocument working layout; see get_formatting_capabilities for syntax and preserve untouched blocks when replacing."

addedInput schema / properties / locale / description
```
Added value: +"Language code, e.g. en or ru."
```

addedInput schema / properties / name / description

Added value: +"Name for the personal template, e.g. Weekly recap."

First observedSep 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world. The description adds meaningful context beyond that: the resulting template is owner-only and nothing is published as a side effect, which tells the agent about visibility and blast radius.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, trigger first, inputs second, effect third. No wasted words or repetition.

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?

An output schema exists, so return values need no explanation, and the description covers trigger, required inputs, and side-effect profile. Only minor gaps remain, such as whether creating a template with an existing name overwrites or fails.

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 each parameter is already documented with examples and constraints. The description only restates the two required inputs (name, RichDocument), adding no syntax or format guidance beyond the schema.

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?

States a specific verb and resource (creates a template) and scopes it to "a reusable post layout." It is distinguishable from publishing/draft siblings by its "without publishing" note, though it never contrasts itself with update_template or list_templates.

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?

Gives an explicit trigger ("when the author asks to save a reusable post layout") and implicitly excludes publishing workflows. No named alternatives or preconditions (e.g. use update_template to change an existing one) are given.

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.