Skip to main content
Glama
Sign In

Postlyra.app — Telegram posts from AI chats

by io.github.prof-1t
OverviewDiscussionsAdmin

Copy a Postlyra post

copy_post

Use when reusing an existing post as a new independent draft. Copies formatting, media and buttons; does not copy publication jobs or publish.

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": {
      "postId": "<postId>"
    },
    "name": "copy_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoSaved-item title, e.g. Weekly recap.
postIdYesOwner-bound postId from search_posts/search_post_drafts/create_post_draft.

Output Schema

NameRequiredDescriptionDefault
dataYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / postId / description
      Added value: +"Owner-bound postId from search_posts/search_post_drafts/create_post_draft."
    • addedInput schema / properties / title / description
      Added value: +"Saved-item title, e.g. Weekly recap."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing exactly what is transferred (formatting, media, buttons) and what is not (publication jobs, publishing), which is the key safety question for a copy operation. It does not note that repeated calls produce distinct drafts (non-idempotent per annotations) or permission requirements, leaving a small gap.

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 compact clauses with the use case front-loaded and the copy-scope caveat second; nothing extraneous or redundant with the title.

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 covers the essential semantics of a copy operation. A note on whether the resulting draft ID is returned or how title interacts with the source would round it out, but the core is complete.

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 are documented in-schema, so the baseline is 3. The description adds no extra meaning about postId sourcing or what the optional title overrides relative to the copied post.

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 ('Copies an existing post as a new independent draft') and immediately scopes the copy to formatting, media and buttons. The 'independent draft' phrasing distinguishes it from create_post_draft and update_post without needing the schema.

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?

Opens with an explicit trigger ('Use when reusing an existing post as a new independent draft') and implicitly excludes publish/schedule flows by noting publication jobs are not copied. It stops short of naming alternatives like create_post_draft or update_post explicitly, so not a full 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