Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Ko-fi post comments

ko_fi_post_comments_list
Read-onlyIdempotent

Lists comments and one level of replies for a Ko-fi post, 25 per page, using the post slug and cursor pagination. Use it to review or moderate discussion around a specific post.

Instructions

List a Ko-fi post's comments and one level of replies, 25 a page. Requires slug. 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": {
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "ko_fi_post_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Post slug from the post URL, e.g. `Shipping-profiles-digital-variants-and-more-D0K429XOFY`.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: replies are only one level deep, page size is 25, and pagination is cursor-based. It does not describe whether comments are ordered, moderated, or filtered, but that is a minor gap given annotation coverage.

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 short sentences, front-loaded with the operation and result shape, then the pagination mechanics. No filler and nothing that could be removed without losing information.

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?

A read-only paginated list with no output schema needs the description to state what comes back and how to continue; it does both ('Returns a list', cursor on pagination) plus the reply depth. It stops short of naming the fields on each comment, which is the only remaining completeness gap for this complexity level.

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 five parameters are already documented, including the slug format and the cursor's same-filters constraint. The description only restates the slug requirement and cursor usage rather than adding new meaning. Baseline 3 applies when the schema does the heavy lifting.

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 post's comments and one level of replies', which tells an agent exactly what is returned, including the reply depth. It does not name or contrast any sibling (e.g. ko_fi_post_get or the platform-specific *_comments_list family), so differentiation is left to the name.

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 by 'Requires `slug`' plus the cursor note for paginated follow-ups, which is enough to call it correctly. There is no explicit when-to-use or when-not guidance versus alternatives such as ko_fi_post_get or other comment-listing tools.

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