Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr discussion replies

flickr_groups_discussions_replies_list
Read-onlyIdempotent

List replies to a Flickr group discussion topic by group and topic ID, with paginated results and cursor support for continuing through long threads.

Instructions

List the replies to a Flickr group discussion topic. Requires groupId and topicId. 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>",
      "topicId": "<topicId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_groups_discussions_replies_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`).
topicIdYesRequired. Discussion topic id, e.g. `72157627531743181`.
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.5/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 profile is fully covered. The description adds only a light pagination hint ('use cursor when paginated'), which the schema already spells out in far more detail. No additional behavioral context (e.g., ordering of replies, whether deleted replies appear) is given.

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 clause about the cursor is largely redundant with the schema's cursor documentation, which keeps it from being maximally efficient.

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 list tool with full schema coverage and rich annotations, the definition is adequate: it states the resource, the required identifiers, and the list return shape. There is no output schema, so a brief note on reply fields or ordering would have improved it, but nothing essential to invoking 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%, including detailed cursor and page semantics, so the schema carries the burden and the baseline of 3 applies. The description adds nothing beyond restating the two required identifiers and gesturing at the cursor, both of which are fully documented in the 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 names a specific verb and resource ('List the replies to a Flickr group discussion topic'), which is clearly narrower than the sibling `flickr_groups_discussions_list` (topics vs. replies). It does not explicitly call out that distinction, but an agent can infer the target resource from the wording alone.

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?

Usage is only implied: the agent learns it needs a group and a topic, but there is no statement of when to prefer this over the discussions or comments siblings, nor any preconditions. 'Requires groupId and topicId' is a prerequisite restated from the schema rather than genuine routing 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