Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Ko-fi creator posts

ko_fi_profile_posts_list
Read-onlyIdempotent

Lists a Ko-fi creator's posts feed with filters for type, audience, and tag, returning 12 items per page and cursor-based pagination for browsing.

Instructions

List a Ko-fi creator's posts feed with optional type, audience and tag filters, 12 items a page. 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_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly posts tagged with this tag, e.g. `build`. Letters, digits, underscores and hyphens only.
pageNoZero-based page index; 12 posts a page. Advance with `page.nextPage` when `hasMore` is true.
typeNoOnly items of this kind: `updates`, `posts`, `images`, `videos`, `audio` or `polls`.
accessNoOnly items the creator set to this exact audience: `public`, `supporters` or `members`. `supporters` does not include `members` items.
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.4/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 the page size (12 items) and that results are a feed plus a cursor for pagination, but it does not disclose ordering, empty-feed behavior, or what happens when filters are combined. Useful but thin beyond the annotations.

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 sentences, front-loaded with the core action and scope, with no filler. The trailing "Returns a list (use cursor when paginated)" is largely redundant with the schema's `cursor`/`page` descriptions, keeping it from a 5.

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 no output schema, the description says only that a list is returned and that cursors exist, without describing item shape or ordering. For a 9-parameter, open-world list tool it is adequate but does not cover the meta-parameters (`context`, `llm_model`, `conversation_id`) or the sequencing constraint mentioned in the schema.

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 nine parameters (including filter enums, cursor reuse constraint, and meta-params) are already documented in the schema. The description only echoes the type/audience/tag filters and the handle requirement, adding no syntax or format meaning 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 specific verb and resource ("List a Ko-fi creator's posts feed") plus the filter dimensions and page size, which is far more than a restated title. It does not differentiate itself from close siblings such as `ko_fi_post_get` (single post) or the other platform `*_profile_posts_list` tools, so an agent must infer the boundary from names alone.

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?

"Requires `handle`" and "use cursor when paginated" give a light usage hint, and the feed framing implies bulk retrieval rather than a single item. There is no explicit when-to-use/when-not guidance or pointer to an alternative (e.g., the single-post tool), leaving routing 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