Skip to main content
Glama
Foto MCP Server
by thesven

foto_create_portfolio

Create and publish a multi-image curated portfolio showcase to Foto with a title, custom cover, alignment, and curated tags; use dryRun to validate images before upload.

Instructions

Create and publish a multi-image curated portfolio showcase to Foto. Includes title, custom cover image selection, alignment, and 1-3 curated tags. Supports dryRun=true.

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": {
      "title": "<title>",
      "images": "<images>",
      "tags": "<tags>"
    },
    "name": "foto_create_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYes1 to 3 tags chosen from Foto's official curated whitelist
titleYesTitle of the portfolio collection (e.g. 'Nordic Nocturnes', 'Tokyo Rain')
dryRunNoIf true, validates and prepares all images without uploading or mutating remote databases
imagesYesOrdered array of at least 2 images for the portfolio
coverIndexNo0-based index of the image to use as the cover (default: 0)
descriptionNoOptional narrative artist statement or description of the collection
coverAlignmentXNoCover thumbnail horizontal alignment (0.0=left, 0.5=center, 1.0=right; default: 0.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that this publishes content to a remote service (a real mutation) and that dryRun avoids remote mutation, which is useful. But it omits auth/permission requirements, whether publishing is immediately public and irreversible, and what the call returns on success or failure.

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 tight sentences, front-loaded with the core action and followed by the notable options. Nothing is padded, though the list of included fields partially duplicates the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter create tool with no output schema and no annotations, the description covers the shape of the operation and the dryRun escape hatch adequately. The remaining gaps (auth requirements, post-publish visibility, error behavior) are real but secondary for an agent that already has a fully documented schema.

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 every parameter including coverIndex, coverAlignmentX, dryRun, and nested image fields is already documented in the schema. The description only restates the highest-level fields and adds no format, ordering, or constraint detail beyond what the schema supplies.

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?

States a specific verb+resource ('Create and publish a multi-image curated portfolio showcase to Foto') and enumerates the notable capabilities (title, cover selection, alignment, 1-3 tags, dryRun). It is clearly distinct from sibling operations like foto_update_portfolio or foto_delete_portfolio by the 'create' verb, though it never explicitly contrasts itself with them.

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 when-to-use or when-not-to-use guidance, and no alternatives are named. The mention of dryRun=true is a capability flag rather than guidance on when a caller should prefer a dry run, so the agent must infer the workflow entirely.

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