Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Flickr user

flickr_users_get
Read-onlyIdempotent

Retrieve a Flickr public profile by user ID or alias, returning identity, counts, links, testimonials, and popular photos for profile analysis.

Instructions

Get a Flickr public profile with identity, counts, links, testimonials and popular photos. Requires userId.

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

Input Schema

NameRequiredDescriptionDefault
userIdYesRequired. NSID (`12037949754@N01`) or path alias (`bees`).
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: the profile is public-only and the payload bundles identity, counts, links, testimonials, and popular photos. It says nothing about error behavior for unknown users or rate limits, and it implies only userId is required while the schema actually requires context, llm_model, and conversation_id.

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 sentences, front-loaded with the resource and its contents, with no filler. The trailing "Requires `userId`" is largely redundant with the schema's required list and its own parameter description, which is the only small waste.

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?

With no output schema, the description usefully summarizes the returned sections at a high level, which is the main thing an agent needs. However, it omits the multi-call protocol implied by the required conversation_id parameter and says nothing about failure modes, so it is adequate rather than complete for a four-parameter tool.

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 all four parameters, including the NSID-versus-alias pattern for userId, are already documented. The description only restates "Requires userId," adding no format or usage detail beyond the schema; baseline 3 applies.

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 gives a specific verb and resource ("Get a Flickr public profile") and enumerates what the profile contains (identity, counts, links, testimonials, popular photos), so an agent knows exactly what comes back. It does not differentiate itself from siblings like flickr_users_search or flickr_users_photos_list, which keeps it out of 5 territory.

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 when-to-use or when-not-to-use guidance and no named alternative. The word "public" hints at scope, but an agent deciding between this, flickr_users_search, and the various flickr_users_*_list tools gets no routing help.

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