Skip to main content
Glama

Schedule / publish a post

flypost_schedule_post
Destructive

Publish a post draft to LinkedIn now, or schedule it for a future time. Carousels need no separate render: if the PDF is missing or older than the slides, this starts the render and the post goes out (or is scheduled) as soon as it finishes, returned as status 'deferred'. Otherwise blocks until the provider confirms (publish-now) or the schedule is registered. A project can hold several identities (the user's profile, teammates' profiles, company pages) — say who to post as with post_as; the choice is recorded on the post and shown in the Posts list and calendar.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "flypost_schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_asNoWho to post as: 'me' (default — the user's own profile), 'company' (the project's company page), or a person's / page's name as listed by flypost_get_linkedin_connection. Fails with the available identities when it does not match exactly one.
draft_idYes
scheduled_atNoFuture ISO timestamp to schedule; omit to publish immediately.
connection_idNoExplicit LinkedIn scheduling identity row id (from flypost_get_linkedin_connection). Overrides post_as.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is known. The description genuinely adds to that: it explains the carousel render trigger, the 'deferred' status when work is async, and that the call otherwise blocks until provider confirmation. It does not address what happens on provider failure, whether publishing is reversible, or any auth/permission requirements for the chosen identity beyond the schema note.

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?

Three sentences, front-loaded with the core action and modes, with the carousel edge case placed after the main path rather than before it. The final sentence about identities is longer than it needs to be, but each piece carries distinct information.

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 4-parameter mutating tool with no output schema, the description covers the important non-obvious behavior: the deferred path, blocking semantics, and identity selection. It still leaves gaps on failure modes and on what a published or scheduled result looks like, which matters for a destructive, open-world write.

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?

At 75% schema coverage the schema already documents post_as, scheduled_at, and connection_id, so the baseline is 3. The description earns a 4 by adding meaning the schema lacks: post_as is recorded on the post and surfaced in the Posts list and calendar, and it names the identities that can be chosen. draft_id, the only required parameter, is still undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a precise verb+resource pair ('Publish a post draft to LinkedIn') plus the two modes (now or scheduled), which is far more specific than the tool name alone. It does not name or contrast any sibling, so an agent must infer on its own how this differs from flypost_prepare_schedule or flypost_cancel_scheduled_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?

The description clearly frames the two usage modes and states that omitting a future time means publish-now, and it explains when post_as matters (multiple identities in a project). It offers no exclusions or explicit alternatives, so it stops short of full routing guidance.

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.