Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Flickr photo comments

flickr_photos_comments_list
Read-onlyIdempotent

Retrieve comments for a Flickr photo by photo ID, returning a paginated list with cursor support for continued review.

Instructions

List Flickr photo comments. Requires photoId. 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": {
      "photoId": "<photoId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "flickr_photos_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.
photoIdYesRequired. Photo id, e.g. `2362225867`.
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
Behavior3/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description does not need to restate safety. It adds that the result is a list and that cursor pagination is available, but it does not disclose ordering, permissions, rate limits, or other behavioral details beyond the 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?

The description is two short sentences, front-loaded with the core action and required parameter, with no unnecessary wording.

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 rich schema coverage and annotations covering safety, the description is largely complete: it states the resource, required id, return shape, and pagination approach. Minor gaps like comment ordering or returned fields are acceptable given the schema and annotations.

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 already documents all seven parameters in detail. The description only repeats the `photoId` requirement and cursor pagination hint, adding no meaning beyond the structured 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 states a specific verb and resource: "List Flickr photo comments," and names the required `photoId`. It is clear what the tool does, though it does not explicitly distinguish itself from sibling comment-listing tools such as `flickr_galleries_comments_list`.

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?

It gives a required-parameter cue (`photoId`) and pagination guidance ("use cursor when paginated"), which implies usage. However, it does not say when to choose this tool over alternatives or when not to use it.

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