Skip to main content
Glama
Foto MCP Server
by thesven

foto_sync_flickr

Migrate and sync Flickr export archives to Foto, normalizing tags, stripping GPS, preventing duplicate publishing, and preparing 1820px zero-crop uploads with a default dry run.

Instructions

Migrate and sync photo archives from a Flickr export (JSON account export or photo JSON files) to Foto. Normalizes tags to 303 whitelist, strips GPS, prevents duplicate republishing, and prepares 1820px zero-crop uploads. Supports dryRun=true (default).

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": {
      "exportPath": "<exportPath>"
    },
    "name": "foto_sync_flickr"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true (default), simulates migration without uploading or creating live posts
mediaDirNoDirectory containing extracted Flickr images (defaults to exportPath directory)
maxPhotosNoMaximum photos to process in this run (default: 20)
exportPathYesPath to Flickr export directory or JSON file
defaultTagsNoOptional default tags to apply if none are suggested

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description does the heavy lifting: it discloses concrete data transformations (tag normalization to a 303 whitelist, GPS stripping, 1820px zero-crop upload preparation) and an idempotency safeguard (prevents duplicate republishing), plus the safe-by-default dryRun behavior. Missing are auth/prerequisite requirements, rate/volume limits, and what a live run actually creates (posts vs. archive entries), which keeps it below a 5.

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?

Two dense sentences, front-loaded with the purpose before the behavioral details, with no filler. The internal jargon ('303 whitelist', '1820px zero-crop') is unexplained but compact, so it earns its space even if an agent may not know what those constraints imply.

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?

For a mutation-capable tool with no annotations and no output schema, the description covers transformations and the dry-run escape hatch well. It still leaves gaps an agent needs before committing to a live run: required Foto authentication state, what the result/report looks like, and whether maxPhotos truncation is silent.

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 all five parameters including defaults for dryRun and maxPhotos are already documented in structured data. The description adds only a restatement of the dryRun default and the export-path content types, so the baseline 3 applies.

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 pair (migrate/sync) plus both the resource (photo archives) and the direction (Flickr export -> Foto). Naming the source platform also separates it from sibling sync tools like foto_sync_instagram and foto_sync_vsco without needing to open any schema.

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 description implies the correct context by naming the required input (a Flickr export, either account JSON or photo JSON files) and states dryRun defaults to true. However, it gives no explicit when-to-use/when-not guidance and never tells the agent how to choose between this and the other foto_sync_* tools beyond the platform name.

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