Skip to main content
Glama

Preview a post before publishing or scheduling

klynx_preview_publish
Read-onlyIdempotent

Use this when the user wants to publish or schedule a saved Klynx post to Facebook or Instagram, before klynx_publish_now or klynx_schedule_post. A dry run: needs post_id, account_ids (from klynx_list_social_accounts, all for the post's platform), caption and image_url (the post's own, word for word, as klynx_create_post_pack returned them), and when (now, or a date and time with its offset, 10 minutes to 30 days ahead), with an optional IANA timezone. Checks the account, the connection, the image, the time and Klynx's limit of 25 posts per account in any 24 hours, and returns exactly what will go out, the account names and a preview_token valid for 15 minutes. Free and changes nothing: it does not publish or schedule. Show the user every detail it returns and ask them to approve before going further.

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": {
      "post_id": "<post_id>",
      "account_ids": "<account_ids>",
      "caption": "<caption>",
      "image_url": "<image_url>",
      "when": "<when>"
    },
    "name": "klynx_preview_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenYesnow, or a date and time with its offset, 10 minutes to 30 days ahead. Example: 2026-11-02T09:00:00+00:00
captionYesThe post's saved caption, word for word: exactly what will be posted.
post_idYesA saved Facebook or Instagram post, from the post_ids of klynx_create_post_pack.
timezoneNoOptional IANA time zone the owner thinks in, for example Europe/London. Defaults to UTC.
image_urlYesThe post's own image URL (enhanced_image_url from klynx_create_post_pack).
account_idsYesaccount_id values from klynx_list_social_accounts, all for the post's platform. Up to 5.

Output Schema

NameRequiredDescriptionDefault
modeYes
reelNo
whenYesnow, or the scheduled instant in UTC.
captionYesExactly what will be posted.
post_idYes
accountsYes
platformYes
timezoneYes
image_urlYes
next_stepYes
publishedYesAlways false: a preview publishes nothing.
scheduledYesAlways false: a preview schedules nothing.
expires_atYes
media_typeNoimage (the post photo) or reel (the post clip as an Instagram or Facebook Reel). Present when the clip tools are offered.
preview_tokenYesPass to klynx_publish_now or klynx_schedule_post with the same details, once the user approves.
scheduled_forYes
uses_allowanceYesAlways false: publishing and scheduling use none of the plan allowance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, but the description adds substantial context beyond them: it is free, changes nothing, checks account, connection, image, time and the 25-posts-per-24-hours limit, and returns a preview_token valid for 15 minutes. That is exactly the behavioral detail an agent needs before invoking a validation tool.

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-loaded with the trigger and alternative routing, then parameters, then behavior — a logical order with no filler sentences. It is a dense single paragraph, though, and the parameter enumeration competes with the higher-value routing and safety statements for attention.

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 6-parameter validation tool with an output schema, the description covers prerequisites, constraints, side-effect profile, and required follow-up (user approval). Return values are described even though an output schema exists, so nothing an agent needs is missing.

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 the baseline is 3. The description's parameter prose ('account_ids from klynx_list_social_accounts', 'word for word', '10 minutes to 30 days ahead', 'optional IANA timezone') largely restates what the schema properties already document, adding little new semantics.

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 — a dry run that previews a saved Klynx post before publishing or scheduling — and explicitly separates it from klynx_publish_now and klynx_schedule_post. An agent can identify what it does and what it is not without opening the 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 an explicit trigger ('Use this when the user wants to publish or schedule...'), positions it before the two downstream siblings, and adds a procedural rule: show the user every detail returned and get approval before going further. When-to-use and when-not-to-use are both covered.

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.

Resources