Skip to main content
Glama
Sign In

Postlyra.app — Telegram posts from AI chats

by io.github.prof-1t
OverviewDiscussionsAdmin

Read a Postlyra post

get_post
Read-onlyIdempotent

Use when reading an existing post and its current revision before editing. Returns the working document without enabling a public preview or publishing anything.

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": {
      "postId": "<postId>"
    },
    "name": "get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesOwner-bound postId from search_posts/search_post_drafts/create_post_draft.

Output Schema

NameRequiredDescriptionDefault
dataYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / postId / description
      Added value: +"Owner-bound postId from search_posts/search_post_drafts/create_post_draft."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: this read does not create a public preview or publish, which is a side-effect distinction the annotations cannot express. It stops short of mentioning auth or revision-conflict behavior.

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?

Two sentences, zero filler, and the usage trigger is front-loaded ahead of the negative scope. Nothing repeats the title or annotations.

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?

With a rich annotation set, an output schema, and a single required parameter, the description covers what an agent needs to select and invoke it. Minor residual gap: nothing about behavior when the post id is stale or belongs to another owner, which matters for an idempotent read.

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 coverage is 100% and the single postId parameter is fully documented in-schema, including its origin tools, so the schema does the heavy lifting. The description adds only the implication that the id refers to an existing post rather than a draft; baseline 3 applies.

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?

States a specific verb and resource (reading an existing post plus its current revision) and immediately scopes it as the pre-edit read. The qualifier 'working document without enabling a public preview or publishing anything' separates it from preview_post and publish_post without requiring the schema to be opened.

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 names the triggering context ('before editing') and explicitly excludes the adjacent operations an agent might confuse it with (preview, publish). That is a when/when-not pairing, not just implied usage.

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 toolsInspect
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.

Resources