flayr

Skip, retry, unschedule, retitle or move a queue item

queue_item_action

DestructiveIdempotent

[PUBLISHES to social accounts · publish scope] action: "skip" passes over a queued item; "retry" puts a failed/skipped item back in line; "unschedule" deletes a booked platform post and puts the item back in line. Also youtubeTitle, per-item platforms, and position (0-based among waiting items). Needs the publish scope (or admin) on the Agency plan or higher. (Wraps PATCH /api/v2/queues/{id}/items/{itemId}.)

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": {
      "id": "<id>",
      "itemId": "<itemId>"
    },
    "name": "queue_item_action"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`action`	No
`itemId`	Yes
`brandId`	No
`position`	No	0-based index among the waiting (queued) items.
`platforms`	No	This item's own platforms, used when it is booked; null → back to the queue's. Only before the item is booked (queued / failed / skipped).
`youtubeTitle`	No	null or "" → back to the draft's stored title.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover readOnly=false, destructive=true, idempotent=true, and openWorld=true. The description adds valuable behavior beyond annotations: the required publish scope/plan, that 'unschedule' deletes a booked platform post, and that per-item platforms can only be set before booking. This is strong additional context, though it does not fully elaborate on all side effects.

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?

The description is a single dense paragraph that front-loads scope and action semantics, and every sentence adds some value. It is slightly run-on but appropriately sized for a multi-action tool with seven parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multi-action, 7 params, no output schema), the description covers action effects, scope, plan requirements, and several parameter meanings. It still omits brandId semantics and does not clarify whether action is optional, leaving gaps for an agent to resolve from schema alone.

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 43%, so the description must compensate. It explains the enum values for action and restates some schema descriptions for position, platforms, and youtubeTitle, which is useful. However, brandId is undocumented in both schema and description, and id/itemId are not elaborated, so the compensation is only partial.

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 description states a specific multi-action verb/resource ('skip', 'retry', 'unschedule' a queue item) and lists what each action does. It is clear enough to distinguish this tool from siblings like add_queue_items or publish, but it does not explicitly differentiate from remove_queue_item or reorder_queue_items, which also manipulate queue items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The per-action semantics imply when each action applies (e.g., retry for failed/skipped items, unschedule for booked posts), and the description states a prerequisite (publish scope or admin on Agency plan). However, it gives no explicit when-to-use vs. siblings or alternatives, leaving the agent to infer routing.

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?