Skip to main content
Glama

Queue library items in bulk

bulk_queue_library
DestructiveIdempotent

Moves up to 50 drafts into the publishing queue by id in one call; they publish automatically at the account's schedule_times. Per-item errors include publishing_in_progress and publish_result_unknown (the item may already be on Threads). Applies when the user approves several drafts at once.

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": {
      "ids": "<ids>"
    },
    "name": "bulk_queue_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesDraft ids (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond what annotations (destructive/idempotent/openWorld) convey: it discloses the automatic publish-at-schedule_times behavior, per-item error semantics, and specifically that publishing_in_progress and publish_result_unknown can occur, warning that an item may already have been posted. That partial-failure detail is exactly the kind of context annotations cannot express.

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?

Three tight clauses, no filler, with the core action and scale limit front-loaded and the error-handling nuance trailing. Every sentence earns its place.

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

Completeness5/5

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

For a one-parameter bulk mutation with no output schema, the description covers scope, scheduling behavior, and failure modes, so an agent has everything needed to call it correctly and interpret per-item errors.

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?

Schema coverage is 100% and there is only one parameter, so the schema already carries the semantics. The description reinforces the id-based targeting and the max-50 limit consistently, adding light value but nothing the schema lacks.

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 and resource ('Moves drafts into the publishing queue by id in one call') plus the scale cap of 50, which cleanly separates it from the singular approve_library_item and from add_library/bulk_archive_library siblings.

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?

Explicitly names the triggering condition: 'Applies when the user approves several drafts at once.' That is clear context, but it does not name an alternative or state a when-not (e.g. use approve_library_item for a single draft), so it falls short of 5.

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.