Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr user favourites

flickr_users_favorites_list
Read-onlyIdempotent

Retrieve a Flickr user's favorited photos by userId, with pagination to browse large collections.

Instructions

List the photos a Flickr user has favourited. Requires userId. 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": {
      "userId": "<userId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_users_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.
userIdYesRequired. NSID (`12037949754@N01`) or path alias (`bees`).
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that a list is returned and that cursor should be used for pagination, without detail on result shape, page-size behaviour, or what happens with a stale cursor — all of which remain in the schema rather than the prose.

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?

Three short sentences with the resource statement front-loaded and no filler. The trailing cursor sentence is largely redundant with the cursor parameter description, which keeps it from being a clean 5.

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?

With seven parameters, no output schema, and 100% schema coverage, the definition is technically callable, but it says nothing about the returned structure (photo objects, IDs, hasMore/nextCursor) even though no output schema exists to fill that gap. Adequate but thin for a paginated list tool.

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%, so every parameter including userId, page, limit and cursor is already documented, and the baseline is 3. The description merely repeats that userId is required, adding no meaning about accepted NSID/alias forms or pagination interaction beyond what the schema states.

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 names a specific verb and resource: listing photos a given Flickr user has favourited, which is clearly distinct from listing a user's own photos (flickr_users_photos_list) or albums. It does not explicitly contrast with the close sibling flickr_photos_favorites_list, leaving a small ambiguity about whose favourites are returned, but the 'a Flickr user' phrasing is reasonably discriminating.

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 or named alternative; the only usage-like statement is 'use cursor when paginated', which restates a preference already documented in the cursor parameter schema. An agent gets no help deciding between this tool and flickr_photos_favorites_list or flickr_users_photos_list.

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