Skip to main content
Glama
Sign In

Sendhour

by com.sendhour
OverviewDiscussionsAdmin

Schedule or publish a post

schedule_post

Schedule a post (or publish it now) on one or more TikTok, YouTube, Instagram, Threads, Bluesky, X or LinkedIn accounts. X posts count toward the workspace's X fair-use allowance (/terms#fair-use-x); each thread part counts. It goes out at scheduled_at without further review, so confirm the content with the user first. TikTok posts publish directly (content_posting_method DIRECT_POST, the default) with the TikTok settings given here; UPLOAD only sends the media to the TikTok app inbox, where the user must finish it.

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": {
      "account_ids": "<account_ids>"
    },
    "name": "schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
duetNoTikTok video posts only: allow duets. Default false.
titleNoYouTube: video title, 2-100 characters. TikTok photo posts: title up to 90 characters.
stitchNoTikTok video posts only: allow stitches. Default false.
threadNoX only: more posts after the caption, posted as a thread (each up to 280 characters). Media goes on the first post.
captionNoPost text. Character limits: X 280 (links count as 23), Bluesky 300, Threads 500, Instagram 2,200, LinkedIn 3,000, YouTube description 5,000.
commentNoTikTok only: allow comments. Default true.
link_urlNoLinkedIn only: share this https link as a card. Not combined with media.
media_idsNoMedia from upload_media_from_url, in order. One video, or photos (TikTok up to 35, LinkedIn up to 20, Instagram/Threads up to 10, Bluesky/X up to 4). YouTube and TikTok need media.
post_typeNoInstagram only. Default post.
link_titleNoLinkedIn only: the link card title (up to 200 characters; LinkedIn does not read it from the page). Defaults to the site address.
visibilityNoYouTube only (required for YouTube).
account_idsYesAccounts to post to (from list_accounts). One post is created per account.
autoAddMusicNoTikTok photo posts only: "yes" lets TikTok add recommended music. Default no.
external_refNoYour own identifier, returned with the post.
scheduled_atNoISO 8601 time with offset, e.g. 2026-10-20T07:30:00-04:00. Omit to publish now. Up to 60 days ahead.
made_for_kidsNoYouTube only: whether the video is made for children.
privacy_levelNoTikTok only: who can view the post. Default PUBLIC_TO_EVERYONE.
video_made_with_aiNoTikTok video posts only: label the post as AI-generated. Default false.
brand_content_toggleNoTikTok only: branded content (paid partnership with a third party); cannot be SELF_ONLY. Default false.
brand_organic_toggleNoTikTok only: the post promotes your own brand. Default false.
content_posting_methodNoTikTok only. DIRECT_POST (default) publishes the post. UPLOAD does NOT publish: it sends the media to the TikTok app inbox, where the user must finish and publish it within 24 hours, and TikTok ignores every other TikTok setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the post 'goes out at scheduled_at without further review', X posts consume a fair-use allowance with each thread part counting, and UPLOAD does not publish but parks media in the TikTok inbox for 24 hours. Annotations (readOnly=false, destructive=false, openWorld=true) already flag this as a non-read write, so these extra consequences are the value-add. Not a 5 because it says nothing about per-account failure behavior when multiple account_ids are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and platform scope, then layers the risk caveats (no review, fair-use quota, TikTok UPLOAD). Dense but every sentence carries operational meaning; the TikTok settings sentence is slightly redundant with the 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 21-parameter, multi-platform, no-output-schema tool, the description covers the highest-risk behaviors: irreversibility of scheduling, quota consumption, and the TikTok non-publishing mode. Missing pieces are the shape of the response (post IDs per account) and partial-failure handling across multiple accounts.

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 one of the 21 parameters is already documented, which sets the baseline at 3. The description reinforces the TikTok content_posting_method semantics and the X thread fair-use accounting, but adds little else beyond what the schema states.

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?

Opens with a specific verb and resource ('Schedule a post (or publish it now)') and enumerates the exact set of supported platforms, which immediately separates it from siblings like create_draft and cancel_post. An agent can tell this is the publish path, not the draft path.

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 concrete decision rules: omit scheduled_at to publish now, use DIRECT_POST versus UPLOAD for TikTok, and confirm content with the user first. It does not explicitly name create_draft as the alternative for unconfirmed content, so the sibling routing is implied rather than stated.

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

All Sendhour 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