Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr user galleries

flickr_users_galleries_list
Read-onlyIdempotent

Fetch a Flickr user's galleries by userId to review their curated photo collections, using cursor pagination for manageable results. Returns list records without totals or cover images.

Instructions

List a Flickr user's galleries; list records have no total or cover images. 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_galleries_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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description contributes one genuine extra fact — that list records omit totals and cover images — which is useful since there is no output schema. It stays silent on auth requirements, visibility of private galleries, and response envelope shape.

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 clauses, front-loaded with the resource and immediately followed by the data-shape caveat, with no filler. The final "Returns a list" clause is mildly redundant against "List ... galleries" but does anchor the pagination hint.

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 read-only list tool with annotations already covering the safety profile and a fully documented schema, the definition supplies the two things an agent most needs: the record-content limitation and cursor guidance. With no output schema, a brief mention of the gallery record fields beyond the negatives would make it fully complete.

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 in the schema. The description only restates "Requires userId" and repeats the cursor preference, adding no syntax or format meaning beyond the structured fields. Baseline 3 applies.

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?

"List a Flickr user's galleries" is a specific verb+resource, and it is distinguishable from siblings like flickr_galleries_get (single gallery) and flickr_galleries_comments_list. The added note that list records carry no total or cover images narrows expectations further, though no sibling is named explicitly to route the agent away.

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?

"use cursor when paginated" is a real usage directive, but it duplicates schema guidance rather than adding scope. There is no statement of when to prefer this over flickr_galleries_get or other per-user listing tools, and no note on whether the user's galleries may be empty or private.

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