Skip to main content
Glama
Foto MCP Server
by thesven

foto_unfollow_user

Unfollow one or more photographers on Foto by user ID or batch. Remove accounts from your following list to control your feed.

Instructions

Unfollow one or more photographers on Foto by user ID(s).

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses only that the operation supports one or many IDs. It omits whether the call is idempotent, what happens when an ID is invalid or not followed, whether authentication is required, and what the result contains for a mutation tool.

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?

The definition is a single front-loaded sentence with no wasted words, and the batch capability is stated compactly. Nothing in the sentence could be removed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is too thin: it leaves auth requirements, failure behavior, and the relationship between the two optional parameters unresolved. It does not give an agent enough to call the tool confidently.

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 both userId and userIds are already documented in the schema, and the description's 'by user ID(s)' merely restates that. With the schema already doing the heavy lifting, baseline 3 is appropriate, though the description does not clarify whether to supply one or the other, or both.

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 states a specific verb and resource (unfollow photographers) and notes batch support via user IDs, so its function is immediately clear. It does not name or differentiate itself from the sibling foto_follow_user beyond the implied inverse, which keeps it below a 5.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no mention of authentication or the login state required to unfollow on a user's behalf. The agent must infer all context.

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