Postlyra.app — Telegram posts from AI chats

Get an auto-signature

get_signature

Read-onlyIdempotent

Use this when managing post auto-signatures. Read this owner-bound auto-signature before editing it. Preserve documentJson and media when making a complete replacement. Never publishes.

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": {
      "signatureId": "<signatureId>"
    },
    "name": "get_signature"
  }
}

Input Schema

Name	Required	Description	Default
`signatureId`	Yes	Owner-bound signatureId from list_signatures/create_signature.

Output Schema

Name	Required	Description	Default
`text`	No
`title`	No
`locale`	No
`display`	No
`message`	Yes
`richHtml`	No
`signature`	Yes
`updatedAt`	No
`previewUrl`	No
`screenshot`	No
`signatureId`	Yes
`documentJson`	No
`inlineButtons`	No
`screenshotUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 29, 2026

addedInput schema / properties / signatureId / description

Added value: +"Owner-bound signatureId from list_signatures/create_signature."

changedOutput schema / properties / display / properties / imageContentIndex / description

Previous value: -"Index of the native image in this response's content array; null when unavailable."New value: +"Native image index in response content; null if unavailable."

changedOutput schema / properties / display / properties / imageMarkdown / description

Previous value: -"Ready-to-use inline image Markdown for the final answer where the host permits remote images. Preserve the leading !."New value: +"Final-answer image Markdown where host allows remote images; keep leading !."

changedOutput schema / properties / display / properties / instruction / description

Previous value: -"How to include the screenshot in the final user-facing answer; a tool-only image or ordinary link is insufficient."New value: +"Screenshot display instructions for the final answer; tool-only images/ordinary links are insufficient."

changedOutput schema / properties / display / properties / suggestedFileName / description

Previous value: -"Filename suggestion for a host-supported attachment made from the returned bytes; not an existing local path."New value: +"Suggested attachment name for returned bytes; not an existing path."

Changed8 schema fields changedOct 13, 2026

removedOutput schema / properties / channelId

Removed value: -{
-  "maxLength": 128,
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / deliveryDocumentJson

Removed value: -{
-  "description": "Composed publication including the selected auto-signature. Edit documentJson, never copy this composition into the post body.",
-  "type": "object"
-}

removedOutput schema / properties / deliveryInlineButtons

Removed value: -{
-  "items": {
-    "anyOf": [
-      {
-        "type": "object"
-      },
-      {
-        "items": {
-          "type": "object"
-        },
-        "type": "array"
-      }
-    ]
-  },
-  "type": "array"
-}

removedOutput schema / properties / draftId

Removed value: -{
-  "maxLength": 128,
-  "minLength": 1,
-  "type": "string"
-}

removedOutput schema / properties / id

Removed value: -{
-  "maxLength": 128,
-  "minLength": 1,
-  "type": "string"
-}

removedOutput schema / properties / signatureSelection

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "mode": {
-      "enum": [
-        "inherit",
-        "none",
-        "custom"
-      ],
-      "type": "string"
-    },
-    "signatureId": {
-      "maxLength": 128,
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "mode"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / signatureSnapshot

Removed value: -{
-  "type": [
-    "object",
-    "null"
-  ]
-}

removedOutput schema / properties / status

Removed value: -{
-  "maxLength": 64,
-  "type": "string"
-}

AddedOct 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description still earns credit by adding the round-trip warning that documentJson and media must be preserved on complete replacement and by confirming "Never publishes" – context an agent would otherwise lack when copying output into update_signature.

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, no filler, and the purpose is front-loaded via "Use this when...". The opener is slightly roundabout compared to leading with the action itself, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return values, and it still flags the fields that matter for downstream edits. Combined with full annotation coverage and a fully described parameter, an agent has everything needed to call it correctly.

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?

The single signatureId parameter is fully documented in the schema, including its owner-bound origin from list_signatures/create_signature. The description adds no format or sourcing detail beyond that, so 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 states the specific action ("Read this owner-bound auto-signature") and its object, which clearly separates it from mutation siblings like update_signature, delete_signature, and assign_signature. It doesn't name those siblings outright, but the read-vs-edit framing makes the distinction inferable.

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?

"Read this owner-bound auto-signature before editing it" gives explicit sequencing guidance that points at update_signature as the follow-on. It stops short of naming the specific alternative tools (preview_signature, list_signatures) or stating exclusions, so it falls below 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.