Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Flickr group

flickr_groups_get
Read-onlyIdempotent

Retrieve a Flickr group's description, rules, privacy labels, and activity by group ID to review group policies and context before joining or interacting.

Instructions

Get one Flickr group's description, rules, named privacy and activity. Requires groupId.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
groupIdYesRequired. Group NSID (`34427469792@N01`) or path alias (`central`).
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 declare readOnly, idempotent, open-world and non-destructive, so safety is covered. The description adds value the annotations cannot: it tells the agent what the payload contains (description, rules, human-readable privacy labels, activity), 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?

Two short sentences with zero waste: the capability and returned fields come first, the required input second. Nothing is buried or repeated.

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-record fetch with no output schema, the description covers purpose, required input and the shape of the return value. It omits what happens for an unknown or private group, and does not steer the agent away from the search tools, but nothing needed to invoke it correctly is missing.

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 groupId parameter already documents both the NSID format and the path-alias form, so the description's "Requires `groupId`" adds nothing new. The three meta-parameters (context, llm_model, conversation_id) are fully documented in the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ("Get one Flickr group") and enumerates the fields it surfaces: description, rules, named privacy and activity. That is far more than a restatement of the title, though it does not explicitly distinguish itself from nearby siblings such as flickr_groups_search or flickr_users_groups_list.

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?

The only usage guidance is the precondition "Requires `groupId`", which the schema already enforces as required. There is no statement of when to prefer this over flickr_groups_search (finding a group) or flickr_groups_photos_list (group content), and no exclusions or error guidance.

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