Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_user_followers

Retrieve and resolve the list of photographers who follow a specific user or yourself on Foto, with optional limits and lookup by user ID or username.

Instructions

Retrieve and resolve the list of photographers who follow a specific user or yourself on Foto.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum follower profiles to return (default: 20)
userIdNoUser ID whose followers to inspect (defaults to authenticated user)
usernameNoUsername handle whose followers to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.2/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. It does not say whether results are paginated, how profiles are ordered, whether both userId and username may be supplied together, or what happens when the target user has no followers or an invalid handle — all material for a read/list tool with zero annotation coverage.

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 efficient sentence with the resource and scope front-loaded and no filler. It is slightly under-specified rather than verbose, so conciseness is good but the sentence could carry more routing detail at the same length.

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-parameter read-only list tool with no output schema and no annotations, the description covers the core action but omits return shape, ordering, and interaction between the two identifier parameters. Adequate but with gaps an agent would notice when composing a call.

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 three parameters (limit, userId, username) are already documented, including the default of 20 and the authenticated-user fallback. The description adds only the notion of resolving profiles, which is marginal beyond the schema; baseline 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?

States a specific verb ('Retrieve and resolve') and resource ('list of photographers who follow a specific user or yourself'), which is clear enough to distinguish it from the sibling foto_get_user_following by direction of the relationship. However, it never names that sibling, so differentiation is left to inference from the wording alone.

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?

The 'or yourself' phrasing implies the default-to-authenticated-user case, but this is already stated in the schema. There is no explicit guidance on when to choose this over foto_get_user_following or foto_get_photographer_profile, and no exclusions or prerequisites are given.

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