Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Gumroad post comments

gumroad_post_comments_list
Read-onlyIdempotent

Retrieve Gumroad post comments and replies, 20 per page, by providing the post ID and creator username; use the returned cursor to fetch additional pages.

Instructions

List Gumroad post comments with their replies, 20 per page. Requires postId and creator. 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": {
      "postId": "<postId>",
      "creator": "<creator>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "gumroad_post_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 1,000. Default: 1.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters; start again without it.
postIdYesRequired. postId, as returned by the Gumroad endpoint that names it.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
creatorYesRequired. Gumroad creator username (the storefront subdomain), e.g. `clifhuman`. A profile URL such as https://clifhuman.gumroad.com/ or https://gumroad.com/clifhuman is also accepted.
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
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 genuine behavioral context beyond that: comments ship with their replies and results arrive 20 per page with a cursor for continuation. It stops short of noting auth requirements, rate limits, or ordering, so it is useful but not rich.

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 with zero filler: scope and page size first, prerequisites second, pagination cue last. Every clause carries information an agent needs before calling.

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 7-parameter read tool with no output schema, the description plus the fully documented schema and rich annotations cover what an agent needs to invoke it correctly. The only soft spot is that "use cursor when paginated" is vague about the page/cursor interaction, though the schema clarifies that cursor is tied to matching filters.

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 page, cursor, postId, creator and the analytics parameters are all documented in the schema itself; the baseline of 3 applies. The description only restates that postId and creator are required and gestures at cursor usage, adding no syntax or format detail the schema does not already give.

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+resource ("List Gumroad post comments") plus two scope facts: replies are included and the page size is 20. Platform naming distinguishes it from the facebook/reddit/lemmy comment-list siblings, but it does not explicitly distinguish it from Gumroad siblings such as gumroad_post_get or the creator-level list tools.

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?

It states prerequisites ("Requires `postId` and `creator`") and gives a pagination hint ("use cursor when paginated"), which implies when to use it — when you have a specific post and need its comments. There is no explicit when-not guidance or routing to the reply/creator-level alternatives.

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