Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr latest uploads

flickr_feed_latest_list
Read-onlyIdempotent

Fetch 20 recent Flickr public uploads, optionally filtered by tags, tag match mode, user NSIDs, or feed language, to source current public photo content.

Instructions

List the newest 20 Flickr public uploads; dateTaken is owner-local with no zone. Optional inputs: tags, tagMode, userId and language. Returns a list.

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_feed_latest_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoSpace- or comma-separated tags.
userIdNoOne NSID or a comma-separated list of NSIDs. Path aliases are not accepted by this feed.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
tagModeNoWhether every tag or any tag must match. Default: all.
languageNoFeed language, e.g. `ja-jp`.
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
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 genuinely useful behavior: a fixed result count of 20, public-only scope, and the caveat that dateTaken is owner-local with no timezone. It omits any mention of rate limits or result ordering, which keeps it short of a 5.

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 scope front-loaded and no filler. The trailing 'Returns a list.' is thin but does confirm output shape in the absence of an output schema, so it narrowly earns its place.

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 simple read-only feed with fully documented parameters and no output schema, the definition covers scope, result count, and the timezone caveat on dateTaken. The main residual gap is how results are ordered and whether they can be paginated beyond the fixed 20.

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 every parameter including tags, tagMode, userId and language is already documented in the schema. The description merely enumerates the same optional inputs without adding format, default, or interaction semantics (e.g., how tagMode pairs with tags). Baseline 3 applies when the schema does the heavy lifting.

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 the newest 20 Flickr public uploads') with a bounded scope of 20 items and public-only visibility. This is distinct enough from siblings like flickr_explore_list or flickr_users_photos_list, though the description never explicitly contrasts itself with them.

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?

There is no guidance on when to choose this feed over flickr_explore_list, flickr_tags_trending_list, or a user-photos feed, and no prerequisites or exclusions. The 'latest uploads' framing implies a recency-based use case, but the agent must infer it.

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