Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr user groups

flickr_users_groups_list
Read-onlyIdempotent

Retrieve the Flickr groups a user belongs to by passing a userId, returning a list for profile, community, or membership analysis.

Instructions

List the groups a Flickr user belongs to. Requires userId. 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": {
      "userId": "<userId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_users_groups_list"
  }
}

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, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds only 'Returns a list,' with no mention of pagination, result caps, or empty-membership behavior, so added behavioral value is minimal but not contradictory. With annotations carrying the load, this sits at an acceptable 3.

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?

Three short sentences, front-loaded with the purpose and with zero padding. The final 'Returns a list' is close to redundant with the verb 'List,' which keeps it just below a 5.

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 listing tool with full schema coverage, complete annotations, and no output schema, the definition supplies enough to call it correctly. Missing pagination/response-shape detail is a minor gap given the annotations already establish the safe read semantics.

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%, and the userId field already documents both NSID and path-alias formats with a regex, so the description's 'Requires `userId`' adds nothing new. Baseline 3 applies because the schema does all the parameter work; the analytics/context parameters are likewise unexplained here but documented in-schema.

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 ('List the groups a Flickr user belongs to'), which is unambiguous and distinct from photo/discussion listing siblings. It stops short of naming a sibling or clarifying scope boundaries (e.g., vs. vimeo_user_groups_list or flickr_users_get), so it is clear but not fully differentiated.

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?

'Requires `userId`' is a prerequisite, not usage guidance; it says nothing about when to choose this tool over flickr_users_get, flickr_groups_get, or the Vimeo equivalent. There are no exclusions or contextual triggers, leaving the agent to infer usage from the name alone.

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