Skip to main content
Glama
Upload-Post

Upload-Post

Official

Mark a queue slot full or free

mark_queue_slot
Idempotent

Mark a profile's posting queue slot as full so the queue skips it, or set full to false to free the slot for scheduling again.

Instructions

Mark one slot of a profile's posting queue as full, so the queue skips it (for example because the user filled it outside Upload-Post), or free it again with full: false. Slot times come from preview_queue.

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": {
      "profile_username": "<profile_username>",
      "slot_datetime": "<slot_datetime>",
      "full": "<full>"
    },
    "name": "mark_queue_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullYestrue marks it full; false frees it.
slot_datetimeYesThe slot time, ISO 8601 in UTC, as preview_queue lists it.
profile_usernameYesUpload-Post profile name.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description adds real semantic context: the marked slot is skipped by the queue and the action is reversible. It does not cover edge cases (marking a slot in the past, a slot that already has a post, error behavior), which matters for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the action, then the rationale, then the inverse mode. Every clause carries information and nothing is repeated from the title.

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 simple three-parameter mutation with full annotations and an output schema, the description covers what it does, why, and where the input values come from. Only interaction with already-scheduled posts and failure conditions are left implicit.

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 all three parameters are already documented, including the `full` semantics and the preview_queue reference for slot_datetime. The description largely restates the `full: false` behavior rather than adding new meaning; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Mark one slot of a profile's posting queue as full') plus the inverse operation via `full: false`, and gives a motivating example. It is clearly narrower in scope than queue-wide siblings like update_queue_settings, though it never names that contrast explicitly.

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?

Provides a concrete when-to-use condition ('because the user filled it outside Upload-Post') and explains the dual mode (mark full vs. free with `full: false`). It also routes the agent to preview_queue for slot times, but lists no exclusions such as what to do when the slot already holds a scheduled post.

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

Deploy Server

Other Tools