Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Flickr gallery

flickr_galleries_get
Read-onlyIdempotent

Fetch a Flickr gallery by gallery ID and return a page of its photos, using page or cursor parameters to continue browsing results.

Instructions

Get one Flickr gallery and a page of its photos. Requires galleryId.

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": {
      "galleryId": "<galleryId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_galleries_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.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
galleryIdYesRequired. Gallery id, e.g. `72157716271339617`.
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
Behavior4/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 real behavioral context by noting the response contains only 'a page of its photos,' signaling partial/paginated results rather than the full photo set. It does not mention auth or rate limits, but the annotation coverage lowers that burden.

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 core action front-loaded and no filler. The second sentence ('Requires `galleryId`') is largely redundant with the required-field schema, a minor wasted clause that keeps it from a 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, a partial-photo-page return, and no output schema, the definition is somewhat thin: it does not explain what a gallery contains or how to obtain a galleryId. The rich schema descriptions carry most of the operational detail, so the description is adequate but not 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 coverage is 100%, so all seven parameters including cursor/limit/page semantics are fully documented in the schema. The description only echoes the required `galleryId`, adding no format, constraint, or meaning beyond structured data, which lands at the baseline 3.

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 gallery') and clarifies the scope includes 'a page of its photos,' which separates it from list-style siblings like flickr_users_galleries_list and flickr_galleries_comments_list. It does not explicitly name or contrast with those siblings, so it stops short of a 5.

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?

The only guidance is 'Requires `galleryId`,' which merely restates a required schema field. There is no direction on when to choose this over flickr_users_galleries_list (to discover IDs) or flickr_albums_get, and no exclusions or prerequisites beyond the parameter.

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