Skip to main content
Glama
Foto MCP Server
by thesven

foto_update_post

Update the caption or tags of an existing Foto post; choose one to three tags from the official curated list.

Instructions

Update the caption or tags of an existing Foto post. Tags must be 1 to 3 items selected from the official 303 curated list.

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_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoNew tags list (1 to 3 curated tags)
postIdYesThe post ID of the post to update
captionNoNew caption or narrative text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the entire behavioral burden. The tag constraint (1–3 items from an official 303-item curated list) is a useful disclosure, but it omits whether the caller must be the post owner, whether unspecified fields are preserved, whether changes are reversible, and what a failure on an unknown postId looks like.

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?

Two sentences with no filler, and the operation is stated before the constraint. Every clause carries information the agent needs.

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 simple three-parameter mutation with no annotations and no output schema, the definition covers the shape of the change and the tag rule but leaves ownership, partial-update semantics, and the response unknown. Adequate as a minimum but not fully complete.

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 coverage is 100%, so each of the three parameters is already documented in the input schema; the description only restates that caption and tags are the mutable fields. It adds the curated-list origin of tags, which is slightly beyond the schema's "curated tags" wording, but no value-range, length, or format detail.

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?

"Update the caption or tags of an existing Foto post" gives a concrete verb (update) plus the exact resource and the mutable fields, which separates it from siblings like foto_delete_post or foto_publish_post. It never names an alternative tool, so it stops short of full sibling differentiation.

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 only implied by the word "existing" — the agent can infer this applies to posts that already exist rather than drafts or new posts. There is no explicit when-to-use statement, no precondition (e.g., must you own the post?), and no routing to foto_draft_post or foto_publish_post.

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