Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Flickr photo

flickr_photo_get
Read-onlyIdempotent

Retrieve a single Flickr photo's metadata—owner, dates, counts, licence, sizes, tags, and notes—using its photoId.

Instructions

Get one Flickr photo with its owner, dates, counts, licence, sizes, tags and notes. Requires photoId.

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": {
      "photoId": "<photoId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_photo_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
photoIdYesRequired. Photo id, e.g. `2362225867`.
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.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds useful return-content context by listing owner, dates, counts, licence, sizes, tags, and notes, which matters because there is no output schema.

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?

The description is a single front-loaded sentence with no wasted wording. The brief requirement statement is redundant with the schema but does not distract from the core purpose.

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 read-only single-photo getter with rich annotations and fully described schema parameters, the description is largely complete. It lists return fields since no output schema exists, though it could mention usage context or the meta-parameters more explicitly.

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 photoId, context, llm_model, and conversation_id parameters are already documented in the schema. The description only repeats that photoId is required and adds no additional parameter meaning beyond the structured fields.

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?

The description states a specific verb and resource: get one Flickr photo. It also enumerates the returned data fields, making the operation concrete, though it does not distinguish this tool from sibling single-photo context or EXIF getters.

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 explicit guidance on when to use this tool versus search, context, EXIF, or other Flickr siblings. The phrase 'Get one' implies single-photo retrieval by id, but the description provides no alternatives or exclusions.

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