Skip to main content
Glama
Foto MCP Server
by thesven

foto_sync_vsco

Migrate VSCO photo exports into Foto by mapping film presets to curated tags, cleaning descriptions, scrubbing GPS, and deduplicating archives, with dry-run simulation by default.

Instructions

Migrate and sync photo archives from a VSCO export (JSON grid/journal export) to Foto. Maps VSCO film emulation presets (e.g. A6, M5, B1, C1, HB2, KP1) to Foto's 303 curated tags, cleans descriptions, scrubs GPS, and deduplicates. 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_vsco"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a lot of work: it discloses preset-to-tag mapping against 303 curated tags, description cleaning, GPS scrubbing, and deduplication, plus the safe-by-default dryRun behavior. It stops short of stating auth requirements, whether re-runs are idempotent, or what happens to photos that fail mapping.

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 that opens with the purpose before listing the transformation steps, with the dry-run caveat last. The preset-name inventory (A6, M5, B1, C1, HB2, KP1) is illustrative but slightly padding given 'film emulation presets' already conveys it.

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 tool with no annotations and no output schema, the behavior of the writes is well covered, but the agent still lacks the return shape (a migration report? counts?), how partial failures are surfaced, and whether Foto auth must be established first. maxPhotos and mediaDir semantics are left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds the only cross-cutting detail an agent needs from prose, that dryRun defaults to true, framing it as a safety default rather than just a boolean. Its mention of the VSCO JSON grid/journal export format also clarifies what exportPath should point at.

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) and both endpoints of the resource (VSCO JSON export -> Foto), plus the concrete transformations applied. The source platform alone distinguishes it from foto_sync_flickr and foto_sync_instagram without needing either 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?

Usage is implied by the description: this is the tool for VSCO exports, and dryRun=true is the default so a safe preview is the natural first call. It never states when to prefer it over other sync tools, prerequisites (e.g. being authenticated first), or when a dry run should be skipped.

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