Skip to main content
Glama
Sign In

Postlyra.app — Telegram posts from AI chats

by io.github.prof-1t
OverviewDiscussionsAdmin

Apply edits to one publication

apply_post_to_publication
DestructiveIdempotent

Use when the author explicitly asks to apply a working post revision to one selected scheduled or delivered Telegram publication. Other destinations stay unchanged. Read the post revision and publicationId first.

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": {
      "publicationId": "<publicationId>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "apply_post_to_publication"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicationIdYesOne delivery/job id from list_publications; distinct from the source postId.
expectedRevisionYesCurrent revision from get_post/last mutation. On conflict reread and compare changes; never bypass revision.

Output Schema

NameRequiredDescriptionDefault
dataYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / expectedRevision / description
      Added value: +"Current revision from get_post/last mutation. On conflict reread and compare changes; never bypass revision."
    • addedInput schema / properties / publicationId / description
      Added value: +"One delivery/job id from list_publications; distinct from the source postId."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the blast radius is scoped to one destination ('Other destinations stay unchanged') and it imposes a read-before-write ordering. It does not restate the destructive overwrite behavior explicitly, but the annotations carry that.

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?

Three short sentences with the trigger front-loaded, followed by scope and prerequisite. No filler and every sentence carries distinct information.

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 full parameter documentation, the description supplies the missing trigger, scope, and prerequisite ordering. It stops short of describing failure modes beyond the revision conflict (which the schema covers) or any limits on editing delivered publications.

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 description coverage is 100%, and both parameters already carry strong inline descriptions including revision-conflict handling. The description only adds the workflow hint to read the revision and publicationId first, which duplicates rather than extends the schema. 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: applying a working post revision to one selected scheduled or delivered Telegram publication. A sibling set containing update_post, update_post_draft, and publish_post makes this differentiation essential, and the description's mention of 'working post revision' and 'one selected ... publication' does that work.

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?

Gives an explicit trigger ('when the author explicitly asks'), which implicitly excludes proactive/automatic application, and states a prerequisite ordering ('Read the post revision and publicationId first'). It does not explicitly name the alternative tools (e.g., update_post, publish_post) or state when not to use it, so it falls 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 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