Postlyra.app — Telegram posts from AI chats

Read publication calendar

list_publications

Read-onlyIdempotent

Use when inspecting scheduled publications, delivery failures or messages previously published by Postlyra. Returns publicationId for rescheduling, cancellation, targeted edits or deletion.

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

Input Schema

Name	Required	Description
`to`	No	Inclusive upper scheduledAt bound as ISO 8601 with UTC offset, e.g. 2026-10-28T18:00:00+07:00.
`from`	No	Inclusive lower scheduledAt bound as ISO 8601 with UTC offset, e.g. 2026-10-28T09:00:00+07:00.
`sort`	No	Default newest first by scheduledAt; use oldest for chronological planning.
`limit`	No	Maximum items to return in this page; observe the schema bounds.
`offset`	No	Zero-based number of matching items to skip; use nextOffset from the preceding page.
`postId`	No	Owner-bound postId from search_posts/search_post_drafts/create_post_draft.
`status`	No	Delivery status filter: queued, sending, sent, retrying, uncertain, failed, blocked_by_limit, canceled or deleted.
`channelId`	No	Owner-bound channel id from list_channels; never invent a recipient.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 29, 2026

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 scheduledAt bound as ISO 8601 with UTC offset, e.g. 2026-10-28T09:00:00+07:00."

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 / postId / description

Added value: +"Owner-bound postId from search_posts/search_post_drafts/create_post_draft."

addedInput schema / properties / status / description

Added value: +"Delivery status filter: queued, sending, sent, retrying, uncertain, failed, blocked_by_limit, canceled or deleted."

addedInput schema / properties / to / description

Added value: +"Inclusive upper scheduledAt bound as ISO 8601 with UTC offset, e.g. 2026-10-28T18:00:00+07:00."

Changed1 schema field changedOct 13, 2026

addedInput schema / properties / sort

Added value: +{
+  "description": "Default newest first by scheduledAt; use oldest for chronological planning.",
+  "enum": [
+    "newest",
+    "oldest"
+  ],
+  "type": "string"
+}

First observedSep 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already disclose readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is fully covered. The description adds a useful note that the result carries publicationId for rescheduling, cancellation, and deletion, but says nothing about pagination behavior or result ordering beyond what the schema implies.

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, front-loaded with the trigger condition, and the second sentence delivers the key downstream value (publicationId). Nothing is redundant or padded.

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-value shape need not be explained, and all 8 parameters are documented in the schema. The description covers the intended scenarios; an extra note on the status filter or pagination strategy would close the remaining gap, but nothing critical 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 coverage is 100% with rich per-parameter descriptions, including bounds, formats, enums, and pagination hints. The description adds no parameter meaning on top of that, so the baseline 3 applies.

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 names a specific resource (publications) and a concrete scope (scheduled, delivery failures, previously published), which is clearly a read/list operation. It doesn't explicitly contrast with the closest siblings, get_post or search_posts, so sibling differentiation is only 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?

The 'Use when inspecting...' clause gives clear triggering conditions, and naming the downstream actions (rescheduling, cancellation, edits, deletion) tells the agent this is the discovery step that feeds those sibling tools. It stops short of stating when NOT to use it, e.g. for a single known post, where get_post is a better fit.

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.