Skip to main content
Glama
Foto MCP Server
by thesven

foto_update_portfolio

Update an existing Foto portfolio showcase by changing its title, description, tags, cover image, or cover alignment. Revise published portfolio details without creating a new post.

Instructions

Update an existing Foto portfolio showcase (title, description, curated tags, cover image ID, or cover horizontal alignment).

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": {
      "postId": "<postId>"
    },
    "name": "foto_update_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoNew list of 1 to 3 curated tags
titleNoNew portfolio title
postIdYesThe portfolio post ID to update
descriptionNoNew artist statement or description
coverImageIdNoNew cover image ID from the portfolio slides
coverAlignmentXNoNew horizontal cover alignment (0.0=left, 0.5=center, 1.0=right)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and does not meet it. It never says whether this is a partial update (omitting a field leaves it untouched) or a replacement, whether 'tags' overwrites the entire curated list, or what permissions/ownership are required — all critical for a mutation with 5 optional fields.

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 with the resource and the mutable fields, no filler. Slightly dense parenthetical enumeration but nothing that should be cut.

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 six-parameter mutation with no annotations and no output schema, the schema fully documents inputs, but the description leaves the partial-vs-full update contract, ownership requirements, and side effects (e.g. tag replacement, cover re-cropping) unexplained.

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%, including the 0.0–1.0 range mapping for coverAlignmentX and the '1 to 3 curated tags' constraint, so the schema does the heavy lifting. The description only mirrors the field list and adds no semantics beyond it, which is the baseline 3 case.

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 ('Update') and resource ('existing Foto portfolio showcase') and enumerates the mutable fields, so it is immediately distinguishable from foto_create_portfolio, foto_delete_portfolio and foto_update_post. It stops short of naming any sibling as an explicit alternative, keeping it at 4 rather than 5.

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?

The word 'existing' implies the post must already be created, but there is no explicit when-to-use guidance, no mention of prerequisites (does the caller need to own the portfolio?), and no routing to foto_create_portfolio vs foto_update_post for non-portfolio posts. Usage is only inferable from the verb.

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