Postlyra.app — Telegram posts from AI chats

Edit a personal template

update_template

DestructiveIdempotent

Use when changing the author's saved template. System templates and other users' templates cannot be edited.

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": {
      "templateId": "<templateId>"
    },
    "name": "update_template"
  }
}

Input Schema

Name	Required	Description
`name`	No	Name for the personal template, e.g. Weekly recap.
`locale`	No	Language code, e.g. en or ru.
`category`	No	Template category label, e.g. news.
`templateId`	Yes	Template id returned by list_templates; select an owner-visible template.
`description`	No	Short description of the template purpose.
`documentJson`	No	Complete RichDocument working layout; see get_formatting_capabilities for syntax and preserve untouched blocks when replacing.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026

addedInput schema / properties / category / description
```
Added value: +"Template category label, e.g. news."
```

addedInput schema / properties / description / description

Added value: +"Short description of the template purpose."

addedInput schema / properties / documentJson / description

Added value: +"Complete RichDocument working layout; see get_formatting_capabilities for syntax and preserve untouched blocks when replacing."

addedInput schema / properties / locale / description
```
Added value: +"Language code, e.g. en or ru."
```

addedInput schema / properties / name / description

Added value: +"Name for the personal template, e.g. Weekly recap."

addedInput schema / properties / templateId / description

Added value: +"Template id returned by list_templates; select an owner-visible template."

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 declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful ownership/auth context (only owner-visible templates are editable) but says nothing beyond that about what gets destroyed or how partial vs. full replacement behaves.

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 short sentences, the usage trigger front-loaded and the restriction immediately after. Nothing is padded or repeated from the title or schema.

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?

For a mutation tool with an output schema, full param descriptions, and annotations covering destructiveness and idempotency, the description supplies the one thing structured fields cannot: the ownership constraint. Only the optional-field/partial-update behavior is left implicit, which is a minor gap.

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%, so the schema already documents all six parameters, including templateId provenance ('returned by list_templates') and documentJson replacement semantics. The description adds no parameter-level meaning, so the baseline 3 is correct.

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?

States the action (changing) and the resource (the author's saved template), and the title adds 'Edit a personal template'. Scope is pinned to the caller's own templates, which separates it from create_template/delete_template, though the verb 'changing' is weaker than 'edits' and no sibling is named 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?

'Use when changing the author's saved template' gives a clear trigger, and the second sentence states an explicit exclusion (system templates and other users' templates). It stops short of naming alternatives such as create_template for new templates or list_templates for lookup, but the when/when-not guidance is otherwise solid.

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.