Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Ko-fi creator membership tiers

ko_fi_profile_tiers_list
Read-onlyIdempotent

Lists a Ko-fi creator's membership tiers, including prices, benefits, previews, and active member counts, so you can compare support options for a given handle.

Instructions

List a Ko-fi creator's membership tiers with prices, benefits, previews and active member counts. 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_tiers_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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuine value by naming the return contents (prices, benefits, previews, active member counts) despite there being no output schema. It stops short of pagination or whether inactive/hidden tiers are included.

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 core action and payload. 'Returns a list.' is largely redundant with the opening 'List', costing a small amount of efficiency but nothing else is padded.

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 simple read-only list tool with full schema coverage and rich annotations, this is nearly sufficient, and the enumerated return fields compensate for the missing output schema. Pagination behavior and result limits are the main unresolved questions.

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, context, llm_model and conversation_id are all documented in the schema. The description only repeats that `handle` is required and adds no semantics about format, case-insensitivity, or page-id alternatives, so the 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 description gives a specific verb and resource ('List a Ko-fi creator's membership tiers') and even enumerates the data returned (prices, benefits, previews, active member counts). The resource itself is distinct from sibling lists like posts, albums, or shop items, though no sibling is named explicitly.

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 implied: fetch tiers for a given creator. The 'Requires `handle`' note signals a precondition, but there is no statement of when to prefer this over a related tool (e.g., profile_get or supporters_list) and no exclusions or edge cases.

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