Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr group discussions

flickr_groups_discussions_list
Read-onlyIdempotent

List a Flickr group's discussion topics by group ID, with pagination and cursor support to browse or continue results.

Instructions

List a Flickr group's discussion topics. Requires groupId. Returns a list (use cursor when paginated).

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_discussions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based. Default: 1. A page past the last returns an empty list with `hasMore: false`. Prefer `cursor` when continuing.
limitNoRows per page, 1 to 100. Default: 100.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters. Send it without `page`; it keeps the page size it was issued with, so `limit` may be sent again and has no effect.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and determinism profile is fully covered elsewhere. The description adds only that it returns a list and that cursor is the preferred continuation mechanism — it says nothing about ordering, treatment of private or restricted groups, or what a topic entry looks like.

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 core capability front-loaded and no filler. "Requires `groupId`" is slightly redundant given the schema marks it required, which keeps this from a perfect score.

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 read-only list tool with no output schema and full schema coverage, the description covers the essentials: required identifier, list return type, and cursor pagination. It omits what an agent might still want — result ordering, roughly expected volume of topics, and whether private-group access is permitted — leaving moderate gaps.

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 seven parameters — including the groupId NSID/alias pattern, cursor semantics, limit behavior, and the context/llm_model/conversation_id meta-params — are already documented in the schema. The description merely restates that groupId is required and repeats the cursor hint, adding no new meaning.

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?

"List a Flickr group's discussion topics" gives a specific verb (list) plus a precisely scoped resource (a single group's discussion topics), which implicitly separates it from flickr_groups_get or flickr_groups_discussions_replies_list. It stops short of naming a sibling or stating that it does not return reply content, so the differentiation is inferred rather than explicit.

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?

"Requires `groupId`" is a precondition and "use cursor when paginated" hints at continuation, which gives implied guidance on how to page. There is no explicit when-to-use vs. when-not-to-use statement, and no pointer to the replies tool for per-topic content.

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