Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Gumroad wishlist items

gumroad_wishlist_items_list
Read-onlyIdempotent

List Gumroad wishlist items 20 per page using a wishlist ID and creator username. Returns paginated results with a cursor for retrieving further pages.

Instructions

List Gumroad wishlist items, 20 per page. Requires wishlistId and owner. 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": {
      "wishlistId": "<wishlistId>",
      "owner": "<owner>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "gumroad_wishlist_items_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 1,000. Default: 1.
ownerYesRequired. 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.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters; start again without it.
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.
wishlistIdYesRequired. wishlistId, as returned by the Gumroad endpoint that names it.
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.5/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile needs no restating. The description adds genuinely new facts: a fixed page size of 20 and that cursors apply to paginated results. It does not say what a page contains or how ordering works.

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?

A single front-loaded sentence with the scope first, then the prerequisites, then the return and pagination note. Nothing is redundant, though three comma-joined clauses make it slightly dense.

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 list endpoint with full annotation coverage and full schema descriptions, the description supplies the missing operational facts: page size, required identifiers, and cursor reuse. Return values are only broadly characterized ('returns a list'), but with no output schema that is a minor gap.

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 every parameter is already documented in the schema, and the description only echoes the two required ones. The one extra detail, the 20-item page size, is a real addition since page size is not a parameter. That is enough for the baseline but not more.

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 Gumroad wishlist items'), which clearly separates it from the singular sibling gumroad_wishlist_get. It stops short of naming that sibling, so differentiation is implied rather than explicit.

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 names the two required parameters and gives one procedural hint ('use cursor when paginated'), which implies iteration workflow. It says nothing about when to choose this list endpoint over a wishlist or product lookup, and no exclusions are stated.

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