Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_post_likes

View the photographers who liked a specific Foto post and resolve their user IDs, usernames, display names, and profile links for audience insights.

Instructions

View the photographers who liked a specific Foto post (/app/liked-by/:postId). Resolves user IDs, usernames, display names, and profile links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postId": "<postId>"
    },
    "name": "foto_get_post_likes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum user profiles to resolve (default: 25)
postIdYesThe post ID to inspect likes for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.4/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 does useful work by disclosing the return payload (resolved user IDs, usernames, display names, profile links) and framing the tool as a read ('View'), but it says nothing about pagination beyond the limit cap, rate limits, privacy of likers, or whether resolution can fail for some IDs.

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 tight sentences, front-loaded with the action and scope, with the route as a compact parenthetical and the return payload summarized in a single clause. Nothing is redundant.

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

Completeness4/5

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

For a two-parameter read tool with a fully described schema and no output schema, the description covers purpose and return contents adequately. The remaining gap is operational detail (auth, pagination, behavior on inaccessible likers) that an agent would want before calling, but it is not a blocking omission.

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%, covering both postId ('the post ID to inspect likes for') and limit ('maximum user profiles to resolve, default 25, max 50'), so the schema does the heavy lifting. The description adds nothing beyond the schema's own wording and does not explain what happens when the limit truncates a large liker list.

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: view the photographers who liked a specific post, with the underlying route '/app/liked-by/:postId'. That clearly separates it from write-side siblings like foto_like_post or foto_unlike_post, though it never explicitly names an alternative tool for comparison.

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 when-to-use guidance at all: no mention of prerequisites (does the post need to be public? must you be authenticated?), no relationship to foto_get_post or feed tools, and no statement of what to do if the post has no likes. The agent must infer usage entirely from the name.

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