Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Ko-fi creator albums

ko_fi_profile_albums_list
Read-onlyIdempotent

Lists a Ko-fi creator's public albums, including titles, cover images and slugs, from a required handle.

Instructions

List a Ko-fi creator's public albums with titles, covers and slugs. Requires handle. Returns a list.

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_albums_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that only public albums are surfaced and names the returned fields, which is useful context, but it says nothing about pagination, ordering, result caps, or behavior for private/unknown handles.

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 compact sentences with the resource and returned fields front-loaded, followed by the requirement and return shape. "Returns a list" is slightly redundant but does carry a little weight given there is no output schema.

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 simple filtered-list tool it covers the essentials, and the returned field names compensate for the absent output schema. However, with four parameters and a list-shaped response, an agent still lacks any notion of pagination, size limits, or empty/error behavior.

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 coverage is 100%, so every parameter, including the handle format and the context/llm_model/conversation_id requirements, is already documented in the schema. The description only restates that handle is required, adding no format, casing, or id-vs-handle nuance beyond what the schema provides; 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 a creator's public albums) plus what each item carries (titles, covers, slugs). It is distinguishable from ko_fi_album_get by being a list over a creator rather than a single lookup, though it never names a sibling to sharpen the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the prerequisite "Requires `handle`", which is a constraint rather than a when-to-use rule. Nothing says when to pick this over ko_fi_profile_gallery_list or ko_fi_album_get, and no exclusions are stated.

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