Skip to main content
Glama

Change a scheduled post

reschedule_post
Idempotent

Change a post that is still QUEUED — move it to a different time, rewrite the caption, swap the media, add or drop a channel, or change which board / Page / company Page / listing it goes to. PASS ONLY WHAT CHANGES: an omitted field is left exactly as it was, and an explicit empty string CLEARS one (linkedinOrganizationId:"" moves a company-Page post back to the person’s own profile). The edited item is re-checked against the identical rules its create passed — visibility the channel can honour, per-channel length, media the channel can carry — so an edit can never slip past a refusal that a create would have caught. Get the id from list_scheduled. Something that already went out cannot be changed: a published post is edited or removed with manage_meta_post / manage_linkedin_post / delete_x_post, not rescheduled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atNothe new time — ISO timestamp (2026-08-05T09:00:00Z) or epoch milliseconds. Must be in the future, at most 365 days out.
idYesthe scheduled post id from list_scheduled
linkNo
pollNoX — replaces the poll; an empty options list removes it.
tagsNoYOUTUBE — replaces the WHOLE tag list; an empty array [] clears the tags.
eventNoGOOGLE BUSINESS — replaces the whole event record {title, startDate, startTime, endDate, endTime}.
offerNoGOOGLE BUSINESS — replaces the whole offer record {couponCode, redeemOnlineUrl, termsConditions}.
titleNoPINTEREST / YOUTUBE — replace the headline; "" clears it and goes back to deriving one from the caption
chatIdNoTELEGRAM — send it to a different chat, group or channel (@username or numeric id). It can be changed but never cleared: telegram cannot publish without one.
pageIdNoFACEBOOK / INSTAGRAM / THREADS — publish from a different connected Page (list_meta_pages)
threadNoX — replaces the WHOLE thread; an explicit [] drops back to a single post using the caption.
altTextNoACCESSIBILITY — replace the screen-reader description(s). A STRING describes every slide; an ARRAY describes them one at a time in slide order and REPLACES the whole list. "" clears it.
boardIdNoPINTEREST — move the Pin to a different board (list_pinterest_boards)
messageNoreplace the caption used for every channel that has no override
captionsNoreplaces the WHOLE per-channel caption map — send every override you want to keep, not just the new one
channelsNoreplaces the channel list
imageUrlNoswap the image; "" removes it
topicTagNoTHREADS ONLY — one topic tag, without the leading #.
videoUrlNoswap the video; "" removes it
imageUrlsNoreplace the CAROUSEL slides, in order; an empty array [] drops the carousel and goes back to a single image. Omit to leave the slides exactly as they are. The edited item is re-checked against the same carousel rules the create passed, so adding a channel that cannot swipe is refused now rather than posting slide 1 later.
slideTextNoPINTEREST CAROUSEL ONLY — per-slide title / description / link, aligned to slide order.
topicTypeNoGOOGLE BUSINESS — the kind of Post; EVENT and OFFER both require `event`.
trialReelNoINSTAGRAM — replaces the trial-reel setting on a queued Reel (MANUAL or SS_PERFORMANCE); an explicit "" turns the trial off and it goes out as an ordinary Reel. Only takes effect while the post is still queued — a Reel already published cannot be converted into a trial.
yourBrandNoTIKTOK — the own-brand disclosure; false turns it off.
actionTypeNoGOOGLE BUSINESS — the call-to-action button; "" clears it.
locationIdNoGOOGLE BUSINESS — a different listing (list_business_locations)
madeWithAiNoX — the AI-media label; false turns it off.
visibilityNoNOTE: changing this without also naming visibilityByChannel clears any per-channel overrides, so "make it all draft" is not a no-op
communityIdNoX — the community to publish into; an empty string goes back to the main timeline.
descriptionNoYOUTUBE — replace the video description; "" clears it. Remember the caption is the TITLE, not the description.
disableDuetNoTIKTOK VIDEO ONLY — block Duets.
quotePostIdNoTHREADS ONLY — the id of the Threads post this one quotes.
countryCodesNoTHREADS ONLY — two-letter country codes limiting who can see the post.
privacyLevelNoTIKTOK — WHICH PRIVACY LEVEL the post goes out at, in TikTok’s own vocabulary. TikTok requires the USER to choose this from the levels their own account allows: call tiktok_creator_info, show them the real options, and pass back the one they picked — never a default and never a guess, which TikTok refuses at init. Omit it and the post falls back to the coarse `visibility` (private → SELF_ONLY, otherwise PUBLIC_TO_EVERYONE), which cannot express MUTUAL_FOLLOW_FRIENDS or FOLLOWER_OF_CREATOR at all. It must agree with the TikTok visibility (SELF_ONLY is the private one) and it is refused on a TikTok DRAFT, which carries no post info.
replyControlNoTHREADS ONLY — who may reply.
xQuotePostIdNoX — the post this one QUOTES; an empty string removes the quote. Named apart from the Threads `quotePostId` on this same schedule.
collaboratorsNoINSTAGRAM — replaces the WHOLE collab list (up to 3 usernames); an explicit [] removes the co-authors and the post goes out as an ordinary single-author post. Only takes effect if the post has not fired yet — an invite already sent cannot be withdrawn from here.
disableStitchNoTIKTOK VIDEO ONLY — block Stitches.
replySettingsNoX — who may reply; "" goes back to everyone.
brandedContentNoTIKTOK — the paid-partnership disclosure; false turns it off.
disableCommentNoTIKTOK — comments off on this post.
linkAttachmentNoTHREADS ONLY — a full http(s) URL rendered as a link card on a TEXT-ONLY post. The only way a Threads post carries a destination.
paidPartnershipNoX — the paid-partnership label; false turns it off.
coverTimestampMsNoTIKTOK VIDEO ONLY — cover frame in milliseconds.
crossreshareToIgNoTHREADS ONLY — also share to Instagram as a Story when it fires; false turns it off. Refused on a carousel.
commercialContentNoTIKTOK — the COMMERCIAL CONTENT DISCLOSURE toggle: true when this post promotes a brand, product or service at all. TikTok requires at least one of yourBrand / brandedContent once it is on, and refuses a post that declares itself commercial without naming which kind. Either disclosure already implies it.
visibilityByChannelNo
crossreshareDarkModeNoTHREADS ONLY — dark-mode that Instagram Story. Needs crossreshareToIg.
linkedinOrganizationIdNoLINKEDIN — target a different company Page, or "" to post as the connected person instead

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by disclosing the partial-update contract (omitted = unchanged, explicit empty string = clear, with a worked example), the re-validation guarantee against the same rules the create passed, and the visibility/visibilityByChannel interaction that can silently clear per-channel overrides. These behaviors are invisible in both the schema and the annotations alone.

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?

Five sentences, zero filler, and the core action is front-loaded in sentence one. The longest sentence (partial-update semantics) is the single most important behavioral fact and earns its length with a concrete clearing example. Every sentence contributes either scope, semantics, validation behavior, id sourcing, or exclusions.

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?

For a 49-parameter mutation tool with no output schema, the description covers the full decision surface: what it does, the update semantics, id provenance, re-validation behavior, and the published-post exclusion with alternative tools. The schema carries per-parameter detail (96% coverage), so nothing an agent needs to invoke it correctly is missing.

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 description coverage is 96%, so the baseline is 3; the description adds the cross-cutting interpretation rule — 'PASS ONLY WHAT CHANGES' with empty-string-clears semantics — which is the key to correctly using all 49 parameters and is not captured in any single schema field. It does not duplicate per-parameter explanations, which the schema already carries.

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?

The description opens with a specific verb and resource — 'Change a post that is still QUEUED' — and enumerates exactly what can change (time, caption, media, channels, destination board/Page/listing). It closes by naming the sibling post-publish tools (manage_meta_post / manage_linkedin_post / delete_x_post) that handle published posts, so an agent cannot confuse reschedule_post with post-publication mutations.

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?

Explicit when-to-use ('still QUEUED') and when-not-to-use ('Something that already went out cannot be changed'), with named alternatives for the excluded case and a direct pointer to list_scheduled for obtaining the id. The condition distinguishing it from the manage_* / delete_* siblings is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

With 293 tools, the surface is enormous and many tools have overlapping purposes—multiple posting tools (post_to_meta, post_to_linkedin, schedule_post, etc.), multiple analytics tools per channel, and several search tools (search_meta_ads, search_instagram, search_reddit...). While each description is detailed, the volume makes it difficult for an agent to reliably distinguish between similar tools without careful reading, leading to frequent misselection.

Naming Consistency4/5

The naming is largely consistent with a verb_noun pattern (post_to_*, list_*, create_*, delete_*, update_*, manage_*). There are clear families for major operations. A few outliers like 'google_business_account', 'hermoso_capabilities', and 'store_get' break the pattern, but the overwhelming majority follow a predictable structure, making navigation somewhat easier.

Tool Count1/5

293 tools is far beyond any reasonable scope for a single MCP server, even for a comprehensive marketing platform. The calibration guide flags 50+ as an extreme mismatch, and this is nearly six times that threshold. Such a large surface overwhelms context windows, increases the probability of misselection, and makes it impractical for agents to learn or use effectively.

Completeness4/5

The tool set covers a vast domain: ad creation and rendering, posting across nine+ social channels, analytics and reporting, file management (Drive/OneDrive), competitor research, brand management, and more. It appears to provide CRUD and lifecycle coverage for most resources. While there may be minor gaps given the immense scope, the overall coverage is impressively comprehensive.