Skip to main content
Glama
Foto MCP Server
by thesven

foto_manage_draft_queue

List, remove, or batch-publish drafts in a persistent local offline queue, with status filters, dry-run validation, and options to clear published or entire queues.

Instructions

List, remove, or batch-publish drafts stored in the persistent local offline draft 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": {
      "action": "<action>"
    },
    "name": "foto_manage_draft_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesQueue operation: 'list' queued drafts, 'publish' pending drafts, or 'remove' drafts
dryRunNoWhen action='publish', set true to validate queued drafts without uploading
statusNoOptional status filter when listing drafts
draftIdNoOptional specific draftId to publish or remove
clearAllNoWhen action='remove', set true to clear the entire draft queue
maxDraftsNoMaximum drafts to publish in a batch (default: 20)
clearPublishedNoWhen action='remove', set true to clear all already-published drafts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses only that the queue is persistent and local; it says nothing about the irreversible nature of 'remove' and 'clearAll', whether publishing uploads to the network (the dryRun parameter hints at it but the description never confirms), or what failure of a queued draft means. For a tool that both mutates and destroys stored data, this leaves significant behavioral gaps.

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?

A single front-loaded sentence with the verbs first and the resource scope after, which is the right ordering. Minor redundancy in 'persistent local offline' costs it the top mark, but nothing is wasted.

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?

The schema is rich and self-documenting, and there is no output schema to explain, so the description only needs to cover behavior. It does not state that removal is destructive or that the queue survives restarts in a way that makes clearAll consequential, leaving the agent to infer risk from parameter names 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 100% and each of the seven parameters has a clear inline description, including enum values and defaults, so the baseline is 3. The description adds no parameter meaning beyond the schema—no explanation of how status filtering interacts with publish, or what happens when both draftId and clearAll are set.

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 names three concrete verbs (list, remove, batch-publish) against a specific resource (drafts in the persistent local offline draft queue), which matches the action enum exactly. It is clear enough to be distinguished from a single-draft queueing tool, but it never names a sibling such as foto_queue_draft or foto_draft_post to make the boundary explicit.

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?

Usage is only implied: the phrase 'persistent local offline draft queue' signals this is for drafts staged while offline rather than immediate publishing, and 'batch-publish' implies bulk operation. There is no statement about when to prefer this over publishing a draft directly, no prerequisites (e.g., being logged in), and no warning about when removal is appropriate.

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