Skip to main content
Glama
Foto MCP Server
by thesven

foto_follow_user

Follow one or more photographers by user ID, with batch support, and update both following and followers lists atomically to keep relationships consistent.

Instructions

Follow one or more photographers on Foto by their user ID(s). Atomically updates following and followers lists.

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

Input Schema

NameRequiredDescriptionDefault
userIdNoA single photographer userId to follow
userIdsNoAn array of photographer userIds to follow in batch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses an atomic side effect ('Atomically updates following and followers lists'), which is real value beyond the schema, but it omits whether the call is idempotent when already following, what happens with an invalid userId, any rate limits, and what the response contains.

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 short sentences, front-loaded with the action and resource, followed by the one behavioral fact that matters. No filler, no restatement of the tool name, and nothing that could be cut without losing information.

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 two-parameter mutation tool with full schema coverage and no output schema, the definition covers the core action and the atomicity of the write. However, with zero annotations it should also state the authentication requirement and the behavior on already-followed or invalid users, which an agent needs before calling it.

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 both parameters carry their own descriptions, so the schema does the heavy lifting. The description's 'one or more ... by their user ID(s)' adds a mild hint that two input modes exist, but it does not resolve the ambiguity that both parameters are optional and does not state whether they are mutually exclusive.

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 uses a specific verb and resource ('Follow one or more photographers on Foto') and names the identifier type used for lookup (user ID(s)). It is clearly distinguishable from siblings like foto_unfollow_user, though it does not explicitly name the inverse operation to reinforce the contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives such as foto_unfollow_user or the follower-listing tools, and no statement of prerequisites (e.g., that the caller must be authenticated). The phrase 'one or more' loosely implies the single-vs-batch parameter split but never says which parameter to prefer or whether both may be supplied together.

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