Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr photos of user

flickr_users_photosof_list
Read-onlyIdempotent

List the photos a Flickr user is tagged in by supplying the required userId; use page and cursor parameters to continue through paginated results.

Instructions

List the photos a Flickr user is tagged in; a walk can repeat a row. 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_photosof_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

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the bar is lower, and the description still adds a genuinely non-obvious trait: "a walk can repeat a row", a duplicate-row warning that no annotation conveys. It also directs pagination continuation to the cursor. It omits auth/API-key requirements and rate limits, keeping it short of a 5.

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?

A single front-loaded sentence plus a parenthetical that carries two independent facts (return shape, cursor preference) with no filler. The phrasing "Returns a list (use cursor when paginated)" is slightly clipped but every clause earns its place.

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 no output schema, the description's "Returns a list" is the only statement about return shape, so the agent gets no picture of photo fields, cursor location beyond the schema's `page.nextCursor`, or empty-result behavior. For a straightforward read-only list over a fully documented schema this is workable, but it leaves the response contract thin.

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 the schema already documents `userId`, `page`, `limit`, and `cursor` in detail. The description restates only that `userId` is required and that cursor is the pagination continuation mechanism, adding little beyond the schema; the three meta-parameters (`context`, `llm_model`, `conversation_id`) go unmentioned but are self-documented.

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 photos a Flickr user is tagged in") and names the required identifier, which separates it from the sibling `flickr_users_photos_list` that presumably lists a user's own photostream. The tag-based scope is a concrete distinguishing detail rather than a restatement of the title.

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?

It states the precondition ("Requires `userId`") and gives a pagination hint ("use cursor when paginated") that matches the schema's own preference for `cursor` over `page`. However, it never says when to prefer this over `flickr_users_photos_search` or `flickr_users_photos_list`, so the agent must infer the selection rule from the name alone.

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