Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Flickr album

flickr_albums_get
Read-onlyIdempotent

Retrieve a Flickr album's details, dates, photo counts, and a paginated photo list using its album ID and owner user ID.

Instructions

Get one Flickr album with its dates, counts and a page of its photos. Requires albumId and userId.

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": {
      "albumId": "<albumId>",
      "userId": "<userId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_albums_get"
  }
}

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. Owner of the album, as an NSID (`8623220@N02`) or a path alias (`bees`). The album must belong to this user.
albumIdYesRequired. Album id, e.g. `72157634976795888`. The album must belong to `userId`.
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.4/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 the response includes dates, counts and a photo page, which is useful return-shape context, but says nothing about pagination behavior or what happens when the album is missing or private.

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 tight sentences with the resource and the return contents front-loaded, and no filler. Slightly too terse to earn a 5, since the second sentence mostly repeats schema-required fields.

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?

For a cursor-paginated single-album read with no output schema, the description should at least hint at pagination and error cases, but it only names the return fields. The unusual required context/llm_model/conversation_id parameters are documented in the schema, though the description never mentions them.

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 page/limit/cursor and the required albumId/userId pairing is fully documented in the schema. The description only restates the two required keys, adding no meaning beyond the structured data; 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?

States a specific verb and resource ("Get one Flickr album") and enumerates what comes back: dates, counts, and a page of its photos. "One" implicitly distinguishes it from the album-list siblings, though no sibling is named explicitly.

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?

The singular "one album" implies this is the single-item lookup versus flickr_users_albums_list, but there is no explicit when-to-use or when-not guidance, and the requirement that the album belong to userId is left to the schema.

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