Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr gallery comments

flickr_galleries_comments_list
Read-onlyIdempotent

Retrieve comments from a Flickr gallery by gallery ID, returning a paginated list with cursor support for continued browsing.

Instructions

List the comments on a Flickr gallery. Requires galleryId. 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": {
      "galleryId": "<galleryId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_galleries_comments_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.
galleryIdYesRequired. Gallery id, e.g. `72157716271339617`.
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 readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds only the `galleryId` requirement and a pagination hint; it says nothing about rate limits, auth needs, or what a comment entry contains.

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?

Three short sentences, front-loaded with the purpose, then the required argument, then the pagination hint. Nothing is wasted and nothing buries the key information.

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 seven-parameter read tool with no output schema, the description is thin: 'Returns a list' does not tell an agent what fields a comment carries or how pagination metadata appears. The heavy-lifting pagination and identity parameters are documented in schema, which prevents this from being worse, but the return side is under-described.

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 the schema fully documents page, limit, cursor, context, galleryId, and llm_model. The description's 'Requires galleryId' and 'use cursor when paginated' merely restate what the schema already explains, so 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?

States a specific verb and resource: 'List the comments on a Flickr gallery.' The word 'gallery' implicitly distinguishes it from photo-comment siblings, but no sibling is named explicitly, so the differentiation is left to inference.

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?

Gives a light nudge toward `cursor` when paginated, which is real usage guidance, but there is no statement of when to choose this tool over flickr_photos_comments_list or flickr_galleries_get, and no prerequisites or exclusions.

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