Skip to main content
Glama
Sign In

Postlyra.app — Telegram posts from AI chats

by io.github.prof-1t
OverviewDiscussionsAdmin

Update Postlyra preferences

update_workspace
DestructiveIdempotent

Use when the author asks to change the account time zone, weekly publication target or content reminder preference. Does not change existing publication times.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNoIANA zone, for example Asia/Bangkok; publication times are stored in UTC.
cadencePerWeekNoDesired weekly publication target, from 0 to 70; used for planning reminders.
remindersEnabledNoWhether content-planning reminders are enabled for this account.

Output Schema

NameRequiredDescriptionDefault
dataYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cadencePerWeek / description
      Added value: +"Desired weekly publication target, from 0 to 70; used for planning reminders."
    • addedInput schema / properties / remindersEnabled / description
      Added value: +"Whether content-planning reminders are enabled for this account."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare this a non-read-only, destructive, idempotent mutation, and the description adds the valuable scope guarantee that publication times are untouched. However, it never explains what makes the call destructive or what gets overwritten, and it does not state whether omitted fields are left unchanged or reset – a material gap for a destructive partial-update tool.

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 sentences, front-loaded with the usage trigger, zero filler, and the scoping caveat placed last where it reads as a guardrail rather than a preamble.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and all three parameters cohere with the description. Still missing, for a destructiveHint=true tool with zero required parameters, is any statement about partial-update behavior and the nature of the destructive risk.

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 timezone format, the 0-70 cadence range, and the boolean semantics; the description merely lists the same three fields. It adds no patch-vs-replace semantics beyond the schema, 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 names the concrete settings being changed (time zone, weekly target, reminder preference), which disambiguates the otherwise vague name 'update_workspace' and pairs naturally against the sibling get_workspace (read vs change). It stops short of explicitly naming get_workspace or the reschedule tools it is distinct from.

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 the author asks to change...' gives a clear trigger condition, and 'Does not change existing publication times' is a useful exclusion that steers the agent away from rescheduling flows. The alternative for time-changing (reschedule_publication) is implied rather than named.

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