Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Flickr photo contexts

flickr_photos_contexts_get
Read-onlyIdempotent

Retrieve the albums and groups that contain a specified Flickr photo by providing its photo ID, so you can see where an image is organized or shared.

Instructions

Get the albums and groups that hold a Flickr photo. 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_contexts_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

B3.1/5.0
Behavior2/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 by structured data. The description adds no behavior beyond that — it does not say whether private/unlisted photos are included, what an empty result means, or whether pagination applies; 'Requires photoId' merely restates the 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?

Two short sentences, front-loaded with the resource definition and followed by the one hard precondition. Nothing is padded or redundant.

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 simple read-only lookup with rich annotations and full schema coverage, this is adequate but thin: it never sketches what 'contexts' actually returns (album/group identifiers or entries), and there is no output schema to fill that gap. The unusual analytics parameters are documented only in the schema, not in the description.

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 baseline is 3. The description's only parameter note is that photoId is required, which the schema already states via `required` and 'Required. Photo id', and it says nothing about the meta-parameters (context, llm_model, conversation_id).

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 names a specific verb and resource: it returns the albums and groups that contain a given photo. That is concrete enough for an agent to distinguish it from flickr_photo_get (single photo metadata) or flickr_albums_get (album metadata), 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says nothing about when to choose this over flickr_photo_get, flickr_photos_favorites_list, or flickr_groups_photos_list, and offers no exclusions or preconditions. Usage is only inferable from the resource description itself.

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