Skip to main content
Glama
Foto MCP Server
by thesven

foto_queue_draft

Stage a validated single photo or multi-image series into a local offline draft queue for later batch publishing.

Instructions

Stage a validated single photo post or multi-image series into the persistent local offline draft queue for later batch publishing.

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": {
      "caption": "<caption>",
      "tags": "<tags>"
    },
    "name": "foto_queue_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYes1 to 3 curated tags from Foto's 303 whitelist
captionYesIntended post caption
filePathNoSingle photo file path (for a single post)
filePathsNo2 to 5 photo file paths (for a multi-image series)
profileNameNoOptional account profile name to associate with this draft

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose meaningful behavior beyond the name: the draft is written to a *persistent local* queue, it is *validated* first, and nothing is published at call time. It omits auth requirements, duplicate-handling, and what happens to entries in the queue afterwards.

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 front-loaded sentence with the verb first and the outcome second; every clause (validated, single vs series, persistent local, batch publishing later) carries information. No filler or redundancy.

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?

With 5 parameters, full schema coverage, and no output schema, the description should say what a successful call returns (e.g., a draft identifier) and whether login is required, and it covers neither. The core semantics of staging versus publishing are covered, but the definition stops short of being self-sufficient for a write tool.

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%, so the baseline is 3. The description adds only marginal meaning, hinting that filePath and filePaths correspond to the single-post versus series cases, but it never states they are mutually exclusive or which is expected when.

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?

Uses a specific verb ("Stage") against a specific resource ("persistent local offline draft queue") and explicitly covers both supported shapes, "single photo post or multi-image series." It implicitly separates itself from direct-publishing siblings by stressing "later batch publishing," but never names an alternative tool outright.

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 phrase "for later batch publishing" implies the use case: staging now, publishing later, presumably offline. There is no explicit when-not guidance, no mention of prerequisites such as being authenticated, and no named alternative for immediate publishing.

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