Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr Explore photos

flickr_explore_list
Read-onlyIdempotent

Fetch a day of Flickr Explore photos by date and paginate through results with page limits or a cursor to continue where you left off.

Instructions

List a day of Flickr Explore photos. Optional inputs: cursor, page, limit and date. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_explore_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay, `YYYY-MM-DD`. Explore began in 2004; earlier days are empty. Default: the latest published day, which is yesterday (UTC) once its list is out and the day before until then.
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.
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, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds only that the return is a list and that cursor is the continuation mechanism; it omits rate limits, empty-day behavior and the default-date behavior that the schema carries.

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 short sentences with the purpose and pagination hint up front. The parameter enumeration is largely redundant with the schema, but it is brief and serves as a quick index.

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?

This is a simple read-only list tool with fully documented schema and clear annotations, so the description covers enough to call it correctly. It is slightly thin on pagination discipline and default-date behavior, but those live in the schema.

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 the schema already explains every parameter in depth, including cursor/page interaction and the date default. The description merely enumerates the optional inputs and adds no syntax or format detail beyond them, matching the baseline.

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 (list a day of Flickr Explore photos) with the scoping unit ('a day') front-loaded. It's clear enough to distinguish from user/tag/group photo lists, though it doesn't explicitly name a sibling it supersedes or complements.

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 parenthetical 'use cursor when paginated' gives real guidance on choosing among the pagination parameters. However, there is no when-to-use vs. alternatives framing and no exclusions (e.g., when to use flickr_photos_search instead).

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