Postlyra.app — Telegram posts from AI chats

Get Postlyra auth status

get_auth_status

Read-onlyIdempotent

Use this when checking the verified Telegram account linked to this AI connection. Show its label when introducing Postlyra or resolving missing channels. The bot must be opened under the same account. Chats connected under another account are not visible here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scopes`	No
`authUrl`	No
`message`	Yes
`authMethod`	No
`authorized`	Yes
`permissions`	Yes
`instructions`	No
`betaDiagnostics`	No
`telegramAccount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

addedOutput schema / properties / telegramAccount

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "accountHint": {
+          "type": "string"
+        },
+        "displayName": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "label": {
+          "type": "string"
+        },
+        "username": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "label",
+        "username",
+        "displayName",
+        "accountHint"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed1 schema field changedOct 13, 2026
- addedOutput schema / properties / betaDiagnostics
```
Added value: +{
+  "type": "object"
+}
```
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 read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context the annotations cannot express: the same-account prerequisite and the visibility limitation for other accounts' chats.

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?

Four short sentences, front-loaded with the trigger ('Use this when...') and followed by purpose, prerequisite, and caveat. No filler, though the visibility caveat and the same-account requirement are close enough in meaning to be consolidated.

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 an output schema present and annotations covering the safety profile, the description need not explain return values. It covers when to call and the account-scoping constraint; the only soft spot is that 'auth status' is described purely as an account label, leaving the nature of the 'status' itself slightly implicit.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-argument tool 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 states a specific verb and resource: checking the verified Telegram account linked to this AI connection, and returning its label. That is clear enough to distinguish it from sibling listing tools like list_channels, though it never names a sibling explicitly.

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?

It gives concrete trigger conditions ('when introducing Postlyra or resolving missing channels') plus a precondition ('the bot must be opened under the same account') and an exclusion ('chats connected under another account are not visible here'). No alternative tool is named for the non-matching case, so it stops short of a 5.

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.