Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Flickr photo EXIF

flickr_photos_exif_get
Read-onlyIdempotent

Fetch a Flickr photo's camera and EXIF tag values by photo ID, with location, serial, and owner metadata removed.

Instructions

Get a Flickr photo's camera and EXIF tags with display values, with location, serial and owner tags removed. 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_photos_exif_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.7/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower. The description still adds genuinely useful context beyond them by disclosing that location, serial-number and owner tags are filtered out of the response, which shapes what the agent will receive. It does not cover authentication or rate-limit behavior.

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 substantive capability and filtering behavior front-loaded. The final 'Requires `photoId`' clause is partly redundant with the schema's required fields, a minor bit of waste in an otherwise tight definition.

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 lookup with no output schema, the description conveys the resource, the return content ('camera and EXIF tags with display values') and the privacy filtering. Nothing critical is missing, though a hint about the response envelope (e.g., grouped EXIF sections) would have completed it.

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%, with each parameter documented in the schema including the photoId pattern and the analytics-only nature of llm_model. The description only restates that photoId is required, which is already the schema's required list, and adds nothing about context, conversation_id or llm_model. Baseline 3 is correct.

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 a Flickr photo's camera and EXIF tags') and scopes it by listing what is stripped from the result. That EXIF focus distinguishes it from the general photo-fetching siblings like flickr_photo_get, though no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is the tool for camera/metadata needs, and the closing sentence states the required photoId. There is no explicit when-to-use versus flickr_photo_get, no prerequisites, and no stated 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