Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr user albums

flickr_users_albums_list
Read-onlyIdempotent

List a Flickr user's albums with photo counts and cover images; use the user ID and cursor pagination to browse all albums.

Instructions

List a Flickr user's albums with counts and cover photos. 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_albums_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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results include counts and cover photos and that pagination uses a cursor, but says nothing about auth requirements, rate limits, or behavior on empty results.

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, front-loaded with purpose and content, then the prerequisite, then pagination. Slight redundancy in restating the userId requirement that the schema already marks as required, but nothing is padded.

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?

With 7 parameters (three of which are analytics/meta fields documented in schema) and no output schema, the description usefully sketches the return shape as a list with counts and cover photos. It is adequate for a read-only list tool, though it could note that page and cursor are mutually exclusive in prose.

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 page, limit, cursor and userId are all fully documented in the schema itself. The description only restates that userId is required and repeats the cursor preference, adding no syntax or format detail beyond the structured fields.

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 gives a specific verb and resource ('List a Flickr user's albums') and adds scope detail about what each entry carries ('counts and cover photos'). It does not name a sibling to distinguish itself from, so an agent must infer that flickr_albums_get is the single-album counterpart.

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 prerequisite ('Requires userId') and gives a pagination hint ('use cursor when paginated'), which is useful context. It offers no explicit when-to-use versus alternatives such as flickr_users_photos_list or flickr_albums_get, so routing guidance is only implied by the resource name.

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