Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr photo favourites

flickr_photos_favorites_list
Read-onlyIdempotent

List everyone who favorited a Flickr photo using its photo ID, and paginate results with a cursor when the list grows.

Instructions

List the people who favourited a Flickr photo. Requires photoId. Returns a list (use cursor when paginated).

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": {
      "photoId": "<photoId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_photos_favorites_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based. Default: 1. A page past the last returns an empty list with `hasMore: false`. Prefer `cursor` when continuing.
limitNoRows per page, 1 to 100. Default: 100.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters. Send it without `page`; it keeps the page size it was issued with, so `limit` may be sent again and has no effect.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
photoIdYesRequired. Photo id, e.g. `2362225867`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that photoId is required and that results are a paginated list keyed by cursor, but says nothing about ordering, empty results, or permission requirements for private/favourited content.

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?

Two short sentences with the operation stated first and the constraint immediately after. Slight redundancy in restating that photoId is required, which the schema's `required` array already enforces, but nothing extraneous otherwise.

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 simple read-only list tool with full schema coverage and no output schema, the description covers what it returns (a list of favouriting users) and how pagination is continued. Missing only minor detail such as item fields or ordering, which is tolerable at this complexity.

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 each parameter (page, limit, cursor, photoId, context, llm_model, conversation_id) is documented in the schema itself. The description only restates that photoId is required and gestures at cursor usage, adding no meaning beyond the structured fields — baseline 3.

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: 'List the people who favourited a Flickr photo' — an agent can tell this is the favouriter-list of a single photo, not a user's favourites. It does not name or contrast against the closest sibling (flickr_users_favorites_list), so differentiation is left implicit.

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?

Usage is only implied by the resource being described; there is no explicit when-to-use versus flickr_users_favorites_list or flickr_users_photosof_list. The 'use cursor when paginated' note gives a small operational steer but is not guidance about tool selection.

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

Deploy Server

Other Tools