Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Ko-fi album

ko_fi_album_get
Read-onlyIdempotent

Fetch a public Ko-fi album and its gallery tiles, 15 per page, using the album slug. Paginate with the returned cursor to retrieve additional pages.

Instructions

Get one public Ko-fi album with its gallery tiles, 15 a page. Requires slug. 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": {
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "ko_fi_album_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Album slug from `/album/{slug}`, e.g. `Belle-Cards-Y8Y616PKXL`.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
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.8/5.0
Behavior4/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 bar is lower. The description still adds real value beyond them: the album must be public, results are paginated at 15 per page, and the return is a list rather than a single object — the latter matters because no output schema exists.

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 resource and behavior, no filler. The "Requires `slug`" sentence is slightly wasteful given the schema marks slug as required, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read fetch with full schema coverage and annotations covering the safety profile. With no output schema, the description compensates by stating the return shape (a list of gallery tiles) and the page size, which is exactly what an agent needs to call and handle the result correctly.

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 slug, cursor, context, llm_model and conversation_id are all documented in the schema. The description only restates the slug requirement and cursor usage that the schema already spells out; it adds no syntax or format detail beyond it. 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 concrete verb and resource ("Get one public Ko-fi album") plus what comes with it ("gallery tiles"), which implicitly separates it from list-style siblings like ko_fi_profile_albums_list and from single-item tools like ko_fi_gallery_item_get. It stops short of explicitly naming an alternative, so the differentiation is inferred rather than stated.

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?

The description gives a pagination condition ("use cursor when paginated") and a hard prerequisite ("Requires `slug`"), which is useful context. It never says when to choose this over ko_fi_profile_albums_list or ko_fi_gallery_item_get, so the when-to-use signal remains implied by the word "one".

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