Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Ko-fi creator gallery

ko_fi_profile_gallery_list
Read-onlyIdempotent

List a Ko-fi creator's gallery tiles with titles, images, and multi-image counts, 20 per page. Pass a handle and use the returned cursor to fetch the next page.

Instructions

List a Ko-fi creator's gallery tiles with titles, images and multi-image counts, 20 a page. Requires handle. 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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "ko_fi_profile_gallery_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
handleYesRequired. A creator's Ko-fi handle (e.g. `ligianunes`) or page id (e.g. `A644275F`). Case-insensitive.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond them by disclosing page size (20 a page) and the shape of each tile (title, image, multi-image count), which helps an agent plan pagination and rendering.

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, front-loaded with the resource and scope, with zero filler. 'Requires `handle`' is slightly redundant with the schema's required list, which keeps it just short of a 5.

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 paginated list with a fully described schema and no output schema, the description covers the essentials: what is listed, page size, return shape, and how to continue pagination. Only a note on authentication or rate limits is missing, which is minor given the rich 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 `handle` and `cursor` are already fully documented, including the note that the cursor only works with the same filters. The description restates 'Requires handle' and mentions cursor usage but adds no new semantics, and it says nothing about the analytics/plumbing params (context, llm_model, conversation_id). Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'List a Ko-fi creator's gallery tiles,' and enumerates the fields returned (titles, images, multi-image counts). This distinguishes it from sibling list tools like albums_list or posts_list by naming the resource precisely, though it never explicitly contrasts with ko_fi_gallery_item_get or ko_fi_profile_albums_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 states the hard prerequisite ('Requires handle') and gives a conditional cue for the cursor ('use cursor when paginated'), which is genuinely useful invocation guidance. However, it never says when to pick this over the single-tile getter or the albums list, so the choice between siblings is left to inference.

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