Skip to main content
Glama
Foto MCP Server
by thesven

foto_list_portfolios

List portfolio showcase collections for a specified or authenticated user, using optional username and limit filters to find relevant portfolios.

Instructions

List portfolio showcase collections for a specific user or the currently authenticated user.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of portfolios to return (default: 20)
userIdNoTarget user ID (defaults to authenticated user)
usernameNoTarget photographer username (e.g. '@alex' or 'alex')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.4/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 behavioral burden. "List" implies a non-mutating read and the description usefully discloses the scope fallback to the authenticated user, but it says nothing about result ordering, whether private portfolios are included, or that authentication is required.

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 well-formed sentence with the resource front-loaded and the target-scope qualifier second; no filler. It is arguably too terse for its complexity, but nothing is wasted.

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 three-optional-parameter read tool with no annotations and no output schema, the definition is minimally adequate. It explains what is listed and for whom, but not what a returned portfolio record contains or how paging interacts with the limit, leaving the agent to discover the response shape empirically.

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% (limit, userId, username all documented, including the '@alex' or 'alex' format), so the baseline applies. The description restates the user-targeting concept but adds no meaning beyond the schema, such as precedence when both userId and username are passed.

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 ("List") with a specific resource ("portfolio showcase collections") and states the scoping rule for whose portfolios are returned. It is clear enough to distinguish this from creation/deletion siblings like foto_create_portfolio or foto_delete_portfolio, though it never names an alternative listing tool such as foto_list_profiles.

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 implied rather than stated: an agent can infer this is the read path for portfolios, and the description explains the default (authenticated user) when no target is given. There is no explicit when-to-use/when-not guidance and no mention of prerequisites such as authentication state, which the sibling foto_auth_status would otherwise gate.

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