Skip to main content
Glama
Sign In

FlipLetters

by com.flipletters
OverviewDiscussionsAdmin

Schedule export on Postiz

flipletters_share_to_postiz

Uploads a cloud media URL (or Studio host local fileName) to a project's Postiz destination and schedules/drafts/posts it. Loop: render_board → list_workspaces → list_postiz_destinations → list_postiz_integrations → share_to_postiz. Requires Authorization: Bearer flk_…. Prefer mediaUrl from flipletters_render_board. Posts publicly to the connected social account when not drafted; confirm the destination and caption with the user before calling. Not idempotent: each call creates another post. If a call fails or times out, confirm with the user before retrying.

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": {
      "workspaceId": "<workspaceId>",
      "destinationId": "<destinationId>",
      "integrationId": "<integrationId>",
      "date": "<date>"
    },
    "name": "flipletters_share_to_postiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesUTC ISO datetime, e.g. 2026-08-14T15:00:00.000Z
typeNoDefault schedule.
contentNoCaption / post body.
fileNameNoLocal renders/*.mp4 name when Studio host has the file.
mediaUrlNoHTTPS URL of the MP4 (from cloud render).
workspaceIdYesFlipLetters project id.
providerTypeNoPostiz provider __type, e.g. tiktok, x, linkedin.
destinationIdYesPostiz destination id on that project.
integrationIdYesPostiz channel/integration id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the annotations by naming the Bearer flk_ auth requirement, the real-world consequence that posts go public to the connected social account unless drafted, and the retry policy. The 'not idempotent: each call creates another post' line restates idempotentHint=false but earns credit by explaining the consequence in concrete terms.

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 purpose, then the prerequisite loop, then credentials, then cautions and retry policy — a sensible ordering with no filler. The loop string is information-dense rather than verbose, though the idempotency sentence slightly overlaps the annotations.

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 9-parameter mutating tool with no output schema, the description covers prerequisites, auth, user-confirmation gates, side effects in the external network, and failure handling. Remaining gaps are minor: no hint about what a successful call returns (post id/status) and no clarification of date semantics for type=now and draft.

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 coverage is 100%, so parameter meaning is already carried by the schema, and the description only adds the preference for mediaUrl over fileName. It does not explain how date interacts with type=now or draft, or that providerType is optional metadata rather than a routing key.

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 concrete verb and resource: uploads a media URL (or local fileName) to a project's Postiz destination and schedules/drafts/posts it. The three-mode outcome (schedule/draft/now) is named, and the naming plus 'Postiz destination' clearly separates it from the sibling flipletters_share_to_team.

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 prerequisite chain (render_board → list_workspaces → list_postiz_destinations → list_postiz_integrations → share_to_postiz) and states the preferred input source, mediaUrl from render_board. It also adds an affirmative gate: confirm destination and caption with the user before calling, and re-confirm before retrying a failed call.

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

All FlipLetters toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources