flayr

Create a posting queue

create_queue

Destructive

[PUBLISHES to social accounts · publish scope] Creates a posting queue. Once items are added it BOOKS REAL POSTS on the given platforms on its cadence (default daily 19:00 America/Chicago, 2 booked ahead). Use startsAt to hold everything until a date. Needs the publish scope (or admin) on the Agency plan or higher. (Wraps POST /api/v2/queues.)

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": {
      "name": "<name>",
      "platforms": "<platforms>"
    },
    "name": "create_queue"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`brandId`	No
`youtube`	No	Queue-wide YouTube defaults (a draft's own options win; titles are per item). YouTube upload options, applied to YouTube targets only. madeForKids is always sent to YouTube (default false). A missing title is derived from the first sentence of the caption, cut to 100 characters at a word boundary. SCHEDULED UPLOADS: the video is uploaded ahead of scheduledAt. "public" is uploaded as private and released by YouTube at the scheduled time; "unlisted" is watchable by anyone with the link from upload time; "private" stays private.
`startsAt`	No	ISO 8601 with an offset (or Z). Nothing is booked before it; the first slot is the first timeOfDay (in the queue's timezone) at or after it, so a startsAt that is itself a slot is the first slot. A past date holds nothing back.
`timezone`	No	IANA timezone. Slots keep their local time across DST.	America/Chicago
`lookahead`	No	How many upcoming items are scheduled at the platform at once.
`platforms`	Yes
`timeOfDay`	No	24-hour "HH:MM" local time.	19:00
`cadenceHours`	No	1, 2, 3, 4, 6, 8, 12, or whole days (24, 48, …, 720).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description goes further by spelling out the external consequence (real posts published to social accounts), the default booking cadence and lookahead, the holding behavior of `startsAt`, and the required scope plus plan tier. That auth/plan gating and scheduling-by-default detail is exactly the context annotations cannot convey.

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 highest-value facts — scope tag, mutation warning, real-post consequence — in a compact multi-clause block with no filler. Slightly dense, but every clause (defaults, scope, plan, endpoint wrapper) carries 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 9-parameter tool with nested youtube options, no output schema and destructive semantics, the description covers the consequential behavior, prerequisites and scheduling defaults well. The main gap is that it never says what the call returns or what to do next (e.g. add_queue_items), which matters more here since there is no output schema.

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 67%, and the description largely restates defaults already present in the schema (daily 19:00 America/Chicago, 2 booked ahead) plus a brief gloss on `startsAt` that is already documented in more depth in the schema. It adds little on name, brandId, platforms, timezone, timeOfDay or cadenceHours allowed values, so it roughly meets the baseline rather than compensating.

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+resource ("Creates a posting queue") and immediately conveys the real-world effect ("BOOKS REAL POSTS on the given platforms"). Combined with the sibling names delete_queue/update_queue/add_queue_items, an agent can distinguish this from the other queue operations without opening a schema.

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 clear operational context: items added later become real bookings, use `startsAt` to hold everything until a date, and the `publish` scope (or admin) on Agency plan+ is required. It does not explicitly name when to prefer it over update_queue or add_queue_items, but the preconditions are well covered.

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

All flayr tools Inspect

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

Need Help?