Skip to main content
Glama
Sign In

Postlyra.app — Telegram posts from AI chats

by io.github.prof-1t
OverviewDiscussionsAdmin

Search Postlyra content

search_posts
Read-onlyIdempotent

Use when finding any existing Postlyra post, including scheduled, published or archived content. Search owner content by words, status, connected channel and update dates. Read the selected post with get_post.

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": "search_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoInclusive upper update-time bound as ISO 8601 with UTC offset, e.g. 2026-10-28T18:00:00+07:00.
fromNoInclusive lower update-time bound as ISO 8601 with UTC offset, e.g. 2026-10-28T09:00:00+07:00.
limitNoMaximum items to return in this page; observe the schema bounds.
queryNoKeywords or fragments in the post title and body; all terms must match. Empty or omitted lists posts.
offsetNoZero-based number of matching items to skip; use nextOffset from the preceding page.
statusNoFilter by the post status, e.g. draft or published.
channelIdNoOwner-bound channel id from list_channels; never invent a recipient.
includeArchivedNoInclude archived posts in results; false by default unless status=archived.

Output Schema

NameRequiredDescriptionDefault
dataYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / channelId / description
      Added value: +"Owner-bound channel id from list_channels; never invent a recipient."
    • addedInput schema / properties / from / description
      Added value: +"Inclusive lower update-time bound as ISO 8601 with UTC offset, e.g. 2026-10-28T09:00:00+07:00."
    • addedInput schema / properties / includeArchived / description
      Added value: +"Include archived posts in results; false by default unless status=archived."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items to return in this page; observe the schema bounds."
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based number of matching items to skip; use nextOffset from the preceding page."
    • addedInput schema / properties / query / description
      Added value: +"Keywords or fragments in the post title and body; all terms must match. Empty or omitted lists posts."
    • addedInput schema / properties / status / description
      Added value: +"Filter by the post status, e.g. draft or published."
    • addedInput schema / properties / to / description
      Added value: +"Inclusive upper update-time bound as ISO 8601 with UTC offset, e.g. 2026-10-28T18:00:00+07:00."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and side-effect profile is fully covered there. The description adds only the scoping note that archived content is searchable and that results are summaries requiring get_post to read — modest added context rather than rich behavioral disclosure.

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?

Three sentences, front-loaded with the trigger condition, with no filler. The middle sentence could be dropped without much loss since the schema enumerates the same filters, but overall the text is compact and well ordered.

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 an 8-parameter, all-optional search tool with an output schema and strong annotations, the description covers purpose, filter dimensions and the read follow-up adequately. The remaining gap is the failure to disambiguate from search_post_drafts, which matters given two search tools in the sibling set.

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 100%, so the baseline is 3; the description earns a notch above by grouping four filters into readable concepts ('words, status, connected channel and update dates') that map onto query, status, channelId and from/to. It still says nothing about limit/offset paging behavior beyond what the schema documents.

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 ('Search owner content' / 'Postlyra post') and enumerates the searchable dimensions (words, status, channel, update dates). It distinguishes itself from get_post by casting that as the follow-up read step, though it never mentions the sibling search_post_drafts, so the boundary versus the other search tool is left implicit.

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?

'Use when finding any existing Postlyra post, including scheduled, published or archived content' gives an explicit trigger condition, and 'Read the selected post with get_post' supplies the follow-up workflow. Missing is any statement of when NOT to use it — e.g. drafts-only lookups that search_post_drafts would serve.

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