Skip to main content
Glama
Foto MCP Server
by thesven

foto_export_vault

Export a complete offline backup of your Foto portfolio to a local directory, including high-resolution photos, EXIF metadata sidecars, and a manifest index.

Instructions

Export a complete offline backup archive of your Foto portfolio: downloads high-resolution 1820px photos, technical EXIF metadata JSON sidecars, and a master manifest.json index.

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": {
      "targetDirectory": "<targetDirectory>"
    },
    "name": "foto_export_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of posts to export (defaults to all)
dryRunNoIf true, previews what will be backed up without downloading images
targetDirectoryYesLocal destination directory path where vault archive will be saved

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does valuable work by disclosing the archive's composition (high-res images, EXIF sidecars, manifest index), which is real behavior beyond the schema. However, for a bulk-download operation it omits significant traits: authentication requirements, expected duration or archive size, whether targetDirectory is overwritten or merged, and whether the download is resumable or rate-limited.

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 sentence, front-loaded with the verb and outcome, followed by a colon-delimited enumeration of archive contents. Every clause carries information an agent can act on, and there is no filler or repetition of the tool name.

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 no output schema, the description usefully compensates by describing what the archive contains, and it covers all three parameters implicitly through the schema. But a bulk-export tool that writes to a local directory warrants disclosure of auth prerequisites, size/time expectations, and overwrite semantics, none of which appear. It is adequate to select the tool, less adequate to call it safely.

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 three parameters (targetDirectory, limit, dryRun) are already documented in the schema. The description adds no parameter-level meaning of its own — it never mentions limit, dryRun, or the destination path. Baseline 3 is the correct ceiling when the schema does all the parameter work.

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 pairs a specific verb ('Export') with a specific resource ('complete offline backup archive of your Foto portfolio') and then enumerates exactly what lands on disk: 1820px photos, EXIF JSON sidecars, and a manifest.json index. That is far more concrete than a restated name. It stops short of 5 only because it never contrasts itself with adjacent siblings such as foto_inspect_image or foto_parse_xmp, which an agent might otherwise consider for metadata retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use statement, no mention of alternatives, and no prerequisites such as being logged in or having a portfolio to export. The backup intent is implied by 'offline backup archive,' but an agent gets no signal about choosing this over a lighter-weight metadata tool, nor any warning about when a full export is inappropriate.

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