Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Flickr user photos

flickr_users_photos_search
Read-onlyIdempotent

Search within one Flickr user's photos by tag or free text, returning paginated results with cursor support for continuing through large collections.

Instructions

Search within one Flickr user's photos by tag or text. 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_photos_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly photos with this tag.
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.
queryNoFree-text search within the user photos.
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 fully covered. The description adds only that userId is mandatory and that results come back as a list with cursor pagination, which is modest additional context. It does not describe result shape or what an empty result means, beyond what the page parameter documentation already says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, zero filler, with the scope constraint front-loaded ahead of the requirement and the return note. Every clause carries information an agent can act on.

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 9-parameter tool with three required parameters and no output schema, the description leaves real gaps: it does not explain how tag and query interact, what happens when neither is supplied, or anything about the returned item fields. The schema compensates for the plumbing parameters, but the search-combination semantics are documented nowhere.

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%, including detailed notes on page vs cursor interaction and limit behavior, so the schema carries the parameter burden. The description merely restates that userId is required and that search is by tag or text. It adds no semantics the schema does not already contain, which puts it 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 a narrowed resource: 'Search within one Flickr user's photos by tag or text.' That scoping implicitly distinguishes it from a global photo search and from a plain user-photo listing. It stops short of naming the sibling it competes with, so an agent still has to infer the choice between this and flickr_photos_search or flickr_users_photos_list.

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 description gives one useful routing rule, 'use cursor when paginated', and states the two search modes (tag or text). It never says when to prefer this over the broader photo search or when a plain user-photo listing is the better call, and it is silent on whether tag and query can be combined.

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