Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Ko-fi creator commissions

ko_fi_profile_commissions_list
Read-onlyIdempotent

Fetch a Ko-fi creator's commission listings by handle to inspect previews, add-ons, waitlist status, and membership requirements; use a cursor to page through results.

Instructions

List a Ko-fi creator's commissions with previews, add-ons, waitlist and membership requirements. 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_commissions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page index. Advance with `page.nextPage` when `hasMore` is true.
limitNoItems per page, 1 to 20. Default: 6.
queryNoSearch term within the commissions.
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

B3.3/5.0
Behavior3/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 the payload scope (previews, add-ons, waitlist, membership requirements) and a pagination hint, but says nothing about rate limits, auth, or result ordering.

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?

Two sentences, front-loaded with what is listed and followed by the required input and pagination note. No redundant or filler wording.

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?

With eight parameters fully described in schema and annotations covering safety, the main gap is the absence of an output schema; 'Returns a list' plus a cursor hint is thin for describing the shape of paginated commission records. Adequate but not complete for a listing tool.

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 all eight parameters are already documented, including cursor/page semantics and the handle format. The description only repeats that `handle` is required and that cursor applies, adding no meaning beyond the schema; 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 Ko-fi creator's commissions') and adds scope detail (previews, add-ons, waitlist, membership requirements). That distinguishes it from the shop-items/tiers/albums siblings, though it never explicitly contrasts with them.

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?

'Requires `handle`' and 'use cursor when paginated' are calling mechanics, not when-to-use guidance. Nothing tells the agent when to prefer this over ko_fi_profile_shop_items_list or the related get-tools, and there are no exclusions.

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