Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Edit scheduled post

edit_scheduled
Destructive

Modify a pending scheduled post in place to reschedule it or fix its text, keeping the same job ID and media; update all platforms or only selected ones.

Instructions

Edit a pending scheduled post in place, keeping its job ID and media: reschedule it (scheduledDate/timezone) and/or fix its text. title and caption rewrite the text for EVERY platform of the post; to change only some platforms, send platformContent instead, e.g. {"instagram":{"caption":"..."},"tiktok":{"caption":"..."}} — platforms not listed keep their text. First comments cannot be edited on a pending post.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYes
titleNoNew title for every platform of the post.
captionNoNew caption/description for every platform of the post.
timezoneNoIANA timezone for scheduledDate.
scheduledDateNoNew date, ISO 8601.
platformContentNoPer-platform text, keyed by platform (instagram, tiktok, youtube, facebook, linkedin, x, threads…). Only the platforms listed are changed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.11.4
    • addedInput schema / properties / caption
      Added value: +{
+  "description": "New caption/description for every platform of the post.",
+  "type": "string"
+}
    • addedInput schema / properties / platformContent
      Added value: +{
+  "additionalProperties": {
+    "additionalProperties": false,
+    "properties": {
+      "caption": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "description": "Per-platform text, keyed by platform (instagram, tiktok, youtube, facebook, linkedin, x, threads…). Only the platforms listed are changed.",
+  "type": "object"
+}
    • addedInput schema / properties / scheduledDate / description
      Added value: +"New date, ISO 8601."
    • addedInput schema / properties / timezone / description
      Added value: +"IANA timezone for scheduledDate."
    • addedInput schema / properties / title
      Added value: +{
+  "description": "New title for every platform of the post.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.11.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false. Beyond that, the description adds real context: the edit is in-place, keeps the job ID and media, only applies to pending posts, and unlisted platforms retain their text. It does not explain what happens if the post is not pending, which would complete the picture.

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?

Front-loads the core action and preservation guarantee, then layers the platform-scoping rule and the first-comment restriction. Every clause earns its place with no filler.

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

Completeness5/5

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

Output schema exists, so return values need no explanation. For a 6-parameter mutation tool with nested objects, the description covers the essential constraints (pending-only, in-place, media preserved, platform scoping) and annotations cover the safety profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so the baseline is 3, but the description adds meaningful semantics: title/caption rewrite text for EVERY platform while platformContent targets only listed platforms, reinforced with a concrete JSON example. This cross-parameter interaction is not derivable from the schema alone.

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 ('Edit a pending scheduled post in place') plus the key invariant that job ID and media are preserved. This clearly distinguishes it from siblings like cancel_scheduled, list_scheduled, and retry_post.

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 explicit routing between `title`/`caption` (all platforms) and `platformContent` (subset of platforms), and warns that first comments cannot be edited on a pending post. It doesn't name an alternative tool (e.g., cancel + recreate) for the non-pending case, so it stops short of full when/when-not guidance.

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