Skip to main content
Glama
gosswerner1-max

LazyRelay MCP Server

by gosswerner1-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_post

Idempotent

Edit a draft, pending, or approval-waiting scheduled post's content, media, tags, or platform settings before publishing. Cannot edit once posting or done; use reschedule to change time.

Instructions

Edit a draft, a post waiting for approval, or a still-pending post: its text, media, tags, options and so on. Not possible once it is posting or done. To change the time, use reschedule_post.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe post id, from list_scheduled_posts
tagsNoUp to 5 short labels for filtering analytics by campaign
boardIdNoPinterest only: the board to pin to. Get it from list_pinterest_boards
contentNoNew text
optionsNoPlatform-specific settings for the account you post to: tiktok {aiGenerated}; youtube {title, privacy public|unlisted|private, madeForKids, tags[], aiGenerated}; instagram {placement feed|reel|story, trialReel, trialGraduation manual|auto}; facebook {placement feed|story}; linkedin {documentUrl (https PDF), documentTitle}; threads, bluesky, mastodon and x {chain: [follow-up texts]} for a thread. Send only the key that belongs to the account's platform.
mediaUrlNoA publicly accessible image or video URL to attach
mediaUrlsNoExtra images after mediaUrl for a multi-image post. Call get_platform_rules for how many the platform takes
firstCommentNoA first comment posted right after publishing (Facebook and Instagram only)
mediaAltTextNoAccessibility description of the main image (Mastodon and Bluesky use it)
coverImageUrlNoA still cover image for a video (Pinterest video pins need one)
selfReplyTextNoA follow-up comment added once the post reaches selfReplyAtLikes likes (Facebook and Instagram only)
destinationLinkNoPinterest only: where a click on the pin goes
selfReplyAtLikesNoThe like count that triggers selfReplyText
tiktokDisableDuetNoTikTok only: turn duets off (default true)
tiktokBrandContentNoTikTok only: the video is a paid partnership
tiktokBrandOrganicNoTikTok only: the video promotes the creator's own brand
tiktokPrivacyLevelNoTikTok only, REQUIRED for TikTok: call get_tiktok_creator_info to see which levels the account allows
tiktokDisableStitchNoTikTok only: turn stitches off (default true)
tiktokDisableCommentNoTikTok only: turn comments off (default true, comments off)
firstCommentDelayMinutesNoWait this many minutes after the post goes live before posting firstComment (0 to 1440, Facebook and Instagram only). 0 or left out posts it right away. Needs firstComment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so safety is covered. The description adds the lifecycle eligibility constraint (edits blocked once posting or done), which is real behavioral context not present in the annotations. It stops short of clarifying whether unlisted fields are preserved or cleared on an update, which matters for a 20-param edit.

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 tight sentences: eligibility first, then the alternative. No filler, and the routing hint is placed at the end where it is easy to act on.

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 20 parameters, full schema coverage, and no output schema, the description covers what the schema cannot: lifecycle eligibility and the reschedule alternative. The remaining gap is update semantics (partial merge vs. full replace of unlisted fields), which an agent editing a complex post would want.

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 every parameter already carries its own documentation (platform scoping, defaults, TikTok requirements). The description only echoes the parameter families ('text, media, tags, options') without adding syntax or format detail beyond the schema, so the baseline of 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 (edit) plus the resource and the exact lifecycle states it applies to (draft, awaiting approval, still-pending), and names the sibling reschedule_post as the tool for a different operation. An agent can separate this from reschedule_post and approve_post without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the when (draft / waiting-for-approval / pending) and the when-not (once posting or done), plus the explicit alternative for changing time. Nothing about routing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools