Skip to main content
Glama
Foto MCP Server
by thesven

foto_update_user_profile

Update an authenticated Foto photographer profile by changing display name, bio, website, or profile photo URL.

Instructions

Update your authenticated Foto photographer profile (displayName, bio, website, or profilePhotoUrl).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "foto_update_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioNoNew biography or artist statement
websiteNoPersonal portfolio website URL
displayNameNoNew display name
profilePhotoUrlNoProfile avatar image URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose that this is a self-scoped mutation requiring authentication. It does not state that omitted fields are left unchanged, whether the change is immediately visible or reversible, or what the response looks like — meaningful gaps for a write operation.

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 front-loaded sentence with the resource named first and the field list parenthetically appended; nothing is wasted or repeated.

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?

This is a simple four-field, zero-required-parameter mutation with no nested objects or output schema, and the field semantics are fully covered by the schema. However, the absence of annotations means the description should have covered partial-update behavior and the effect of the write, which it omits.

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 four parameters are already documented in the schema, and the description merely repeats the field names. It adds no format constraints, validation rules, or guidance on combining fields, so the baseline of 3 applies.

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 gives a specific verb ('Update') and resource ('your authenticated Foto photographer profile') and enumerates the mutable fields, which cleanly separates it from siblings like foto_update_portfolio or foto_update_post. It stops short of explicitly naming an alternative tool, but the field list does the disambiguating work.

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?

'your authenticated ... profile' implies the scope is limited to the caller's own profile and that authentication is a precondition, which is useful implicit guidance. There is no explicit when-to-use versus when-not-to-use statement, no mention of sibling tools for portfolio/post updates, and no note that all fields are optional so partial updates are allowed.

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