Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_user_following

Retrieve and resolve the photographers a Foto user or authenticated account follows, with optional user ID, username, and result limit controls.

Instructions

Retrieve and resolve the list of photographers that a specific user or yourself is following 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_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum following profiles to return (default: 20)
userIdNoUser ID whose following list to inspect (defaults to authenticated user)
usernameNoUsername handle whose following list 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 signals a read operation but omits whether authentication is required, how private accounts behave, pagination/ordering of results, and what happens when both userId and username are supplied.

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 front-loaded sentence with no padding. 'Retrieve and resolve' is slightly redundant, but the sentence is efficient and information-dense.

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 read tool with fully described optional parameters and no output schema, the definition covers the essentials. It still leaves gaps on result shape (photographer profiles), pagination behavior, and authentication expectations that an agent would benefit from knowing.

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 all three parameters are documented in the schema, and the description only echoes the default-to-authenticated-user behavior. Baseline 3 is appropriate since the schema does the detailed work and the description adds little parameter-level meaning.

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 ('Retrieve and resolve the list of photographers that a specific user or yourself is following'), with clear scope covering both self and other users. The 'following' framing inherently distinguishes it from the sibling followers tool, though it never names that sibling.

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?

Implies usage via 'a specific user or yourself', clarifying that no identifier yields the authenticated user's list. However, it gives no explicit when-to-use versus foto_get_user_followers or foto_get_user_profile, and no prerequisites such as authentication or private-account handling.

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