Skip to main content
Glama

Preview a post (dry run)

preview_post
Read-onlyIdempotent

Checks a post exactly as publishing would (accounts, caption and title limits per network, video length, schedule, TikTok audience) without sending or spending anything. caption is the text everywhere; overrides sets a different caption or title per network (e.g. {"youtube": {"title": "…"}, "tiktok": {"caption": "…"}}). For a TikTok account, tiktok.privacy_level is required: ask the user who can view it (never choose for them); an issue lists the allowed values when it is missing or not allowed. Always call this first and show the user the result; then publish_post with the same arguments.

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": {
      "video_id": "<video_id>",
      "profile_id": "<profile_id>",
      "account_ids": "<account_ids>",
      "caption": "<caption>",
      "mode": "<mode>"
    },
    "name": "preview_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes'now', 'schedule' (needs scheduled_at) or 'queue' (the profile's next free slot)
titleNoTitle for titled networks (YouTube); required when one is targeted
redditNoRequired when a Reddit account is targeted
tiktokNoTikTok settings, used when a TikTok account is targeted. Ask the user who can view it (privacy_level) before preview_post.
captionYesPost text on every network (on YouTube: the description)
timezoneNoIANA zone, e.g. Europe/Madrid (default: the server default)
video_idYesA ready video (list_videos / get_video status "ready")
overridesNoPer network (tiktok, instagram, youtube, facebook, linkedin, threads, reddit, bluesky): a different caption and, on titled networks (YouTube), a different title. Networks left out use caption / title.
profile_idYesThe profile to post from (list_profiles)
account_idsYesAccounts of that profile to post to (list_profiles, postable: true)
ai_generatedNoLabel the post as AI-generated where the network supports it (default: true for AI swaps, false for your own videos)
scheduled_atNoLocal time YYYY-MM-DDTHH:mm in `timezone`
first_commentNoPosted as the first comment where the network supports it
youtube_privacyNoYouTube visibility (default public)

Output Schema

NameRequiredDescriptionDefault
okYes
issuesYes
dry_runYes
posts_neededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds material behavior beyond them: it spends nothing, it mirrors publish-time validation, and it discloses that an issue object lists allowed values when TikTok privacy_level is missing or invalid. It also adds a human-in-the-loop rule (never choose the TikTok audience for the user), which is not derivable from any annotation.

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?

It is front-loaded with the dry-run purpose and the call-order rule, and every sentence carries operational value. The only minor redundancy is restating the TikTok privacy_level requirement, which also appears verbatim in the schema's field description.

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 14-parameter, nested-object tool with an output schema, the description covers what an agent most needs: the dry-run contract, the follow-up call, the per-network caption model, and the one required user decision (TikTok privacy). Return-value explanation is unnecessary given the output schema, and the remaining field details are fully covered in the schema.

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?

With 100% schema coverage the baseline is 3, and the description earns a step above by clarifying the caption/overrides relationship ('caption is the text everywhere') and giving a concrete overrides example with per-network title vs caption. It does not add format detail for the remaining parameters such as scheduled_at, timezone, or ai_generated, but those are well documented in the schema.

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 concrete verb and resource plus scope: it checks a post exactly as publishing would, without sending or spending anything. It enumerates what is validated (accounts, caption/title limits per network, video length, schedule, TikTok audience), which makes the purpose unmistakable and distinct from publish_post.

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?

It gives an explicit directive: 'Always call this first and show the user the result; then publish_post with the same arguments.' The alternative (publish_post) and the sequencing condition are both named, and the user-facing obligation to display results is stated.

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.