Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Ko-fi creator top supporters

ko_fi_profile_supporters_list
Read-onlyIdempotent

Retrieve a Ko-fi creator's ranked supporters with rank and avatar—up to ten from the leaderboard or the top three—by providing the creator's handle.

Instructions

List a Ko-fi creator's ranked supporters, up to ten from the leaderboard or else the top three, with rank and avatar. 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_supporters_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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety burden is lifted, and the description still contributes real behavioral detail: the 10-from-leaderboard-else-3 fallback and the included rank/avatar fields. It omits the empty-supporters case and any rate-limit or auth context, keeping it below a 5.

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 core behavior and the leaderboard fallback. "Returns a list" is near-zero information and "Requires `handle`" duplicates the schema's required list, which keeps it from a perfect score.

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 read-only list tool with full schema coverage this is largely sufficient, but with no output schema the phrase "Returns a list" leaves the response shape (items, fields per supporter, ordering) underspecified. The documented fallback behavior helps but does not fully cover what an agent would want to know about results.

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%, including the handle pattern, page-id alternative, and case-insensitivity, so the schema does the heavy lifting. The description only restates that `handle` is required and adds no semantics for `context`, `llm_model`, or `conversation_id` beyond what the schema already explains; 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?

The definition opens with a specific verb+resource pair ("List a Ko-fi creator's ranked supporters") and names the exact payload (rank, avatar), which is clearly distinct from sibling list tools for posts, albums, shop items, and tiers. It stops short of explicitly contrasting itself with `ko_fi_profile_get`, so it is clear but not fully sibling-differentiated.

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?

Usage is only implied: an agent can infer it is the right call when a creator's supporters are wanted. The description states the `handle` prerequisite but gives no when-not-to-use conditions and names no alternative tool, so selection against 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