Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_photographer_profile

Retrieve a photographer's public Foto profile by user ID or username, including bio, follower counts, profile link, and sample works.

Instructions

Look up any photographer's public profile on Foto by user ID or username. Returns bio, follower counts, profile link, and sample works.

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

Input Schema

NameRequiredDescriptionDefault
userIdNoThe photographer user ID
usernameNoThe photographer username / handle (with or without @)

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?

No annotations are supplied, so the description carries the full burden. It implies a read-only, public-data operation and discloses the return payload ('bio, follower counts, profile link, and sample works'), but says nothing about authentication, visibility restrictions on private accounts, or what happens when no match is found.

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, zero padding, with the action and lookup keys front-loaded and the return contents in a compact trailing clause. Every sentence earns its place.

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?

With no output schema, describing the returned fields is the right call and is done well. However, for a lookup tool with two optional parameters and zero required ones, the definition never states whether one identifier is mandatory or what a failed lookup yields, leaving a real gap for correct invocation.

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% and the schema already documents both fields, including that the handle may include '@'. The description adds only the useful implication that either identifier alone is sufficient for lookup, which is baseline-level added value.

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 and resource ('Look up any photographer's public profile on Foto') plus the two lookup keys, which is more than a restatement of the name. It does not, however, distinguish itself from the near-identical sibling foto_get_user_profile, leaving an agent to guess which of the two profile lookups applies.

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 by 'Look up any photographer's public profile ... by user ID or username', which tells the agent the accepted identifiers. There is no when-to-use versus when-not guidance and no mention of the sibling profile tools that would make the choice unambiguous.

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