Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Gumroad creator posts

gumroad_creator_posts_list
Read-onlyIdempotent

List every post title, slug, and date a Gumroad creator's profile exposes by supplying the creator username or profile URL. Returns a list for content tracking or analysis.

Instructions

List every post title, slug and date a Gumroad creator's profile exposes. Requires creator. 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": {
      "creator": "<creator>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "gumroad_creator_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the result set is exhaustive ("every post") and enumerates the returned fields, which is useful given there is no output schema, but it says nothing about pagination limits, ordering, or behavior when the creator has no posts.

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 payload description and then the prerequisite. "Returns a list." is near-redundant with "List every post" and is the only wasted line.

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?

This is a simple read-only enumeration tool whose annotations cover the safety profile, and the description compensates for the missing output schema by naming the returned fields. The remaining gap is pagination/ordering behavior, which is minor for a list tool of this shape.

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%, and the creator parameter is documented in detail in the schema (username or profile URL). The description only restates that `creator` is required, adding no meaning beyond the structured field, 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 states a specific verb and resource ("List every post title, slug and date a Gumroad creator's profile exposes") and even names the fields returned. It does not explicitly contrast with the closest sibling gumroad_creator_products_list, but the resource is unambiguous enough that an agent can distinguish posts from products.

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?

There is no when-to-use guidance, no exclusions, and no reference to alternatives such as the creator detail or products tools. The only guidance is the prerequisite "Requires `creator`", which is already enforced by the schema's required array.

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