Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Gumroad products

gumroad_products_search
Read-onlyIdempotent

Search Gumroad products by query, category, tags, price, rating, and file type to find digital products matching specific buyer criteria. Supports sorting and pagination for targeted product research.

Instructions

Search Gumroad products by text, category, tags, price, rating and file type. Optional inputs: query, sort, category, tags, fileTypes and 7 more. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "gumroad_products_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 1,000. Default: 1. A search stops at 10,000 results; narrow the query or add filters for deeper pages.
sortNoHow results are ordered. `hot_and_new` narrows the set to recent products with traction; the others only reorder it. Default: Gumroad's default order.
tagsNoTag names, OR-ed. Up to 10.
limitNoRows per page, 1 to 100. Default: 20.
queryNoSearch text, in any language. Empty or omitted browses every product.
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.
categoryNoCategory path from the categories endpoint, e.g. `3d/3d-modeling`. An unknown path is not rejected; Gumroad ignores the filter and the results are unfiltered.
maxPriceNoMaximum price in whole units of the product's own currency, e.g. `10` for $10, not cents. The filter compares a tier or suggested price, so a row's listed price can differ. A EUR product is compared in EUR.
minPriceNoMinimum price in whole units of the product's own currency, e.g. `5` for $5, not cents. The filter compares a tier or suggested price, so a row's listed price can differ. A EUR product is compared in EUR.
fileTypesNoFile types such as `pdf`, OR-ed. Up to 10.
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.
minRatingNoOnly products rated at least this many stars, 1 to 5.
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.
attributeFiltersNoCategory attribute filters of the form `name:value`, e.g. `product_type:script`. Requires `category`; up to 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered. The description adds only that results come back as a list and that cursors apply when paginated, which largely restates the cursor parameter documentation rather than adding new behavioral context such as empty-result behavior or filter-combination semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the search facets, which is good. The second sentence is padded: it enumerates six parameters and then waves at '7 more', which is noise rather than useful information and could have been replaced by a single statement about filtering.

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?

For a 15-parameter search tool with no output schema, the description covers the high-level purpose and flags pagination, which is the minimum needed to call it. It omits anything about result shape beyond 'a list' and gives no hint that required context/llm_model fields exist, though the schema documents those thoroughly.

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 per-parameter text is unusually rich (currency nuance for min/maxPrice, OR-ed tags, category paths silently ignored when unknown). The description only names a subset of parameters and says 'and 7 more', adding no meaning beyond the schema, 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?

States a specific verb and resource plus the facets it searches (text, category, tags, price, rating, file type), so an agent immediately knows this is a faceted product search. It does not distinguish itself from nearby siblings such as gumroad_creator_products_list or the marketplace-specific product search tools, so the agent must infer the boundary.

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 or when-not-to-use guidance and no alternative tool is named. The only procedural hint is 'use cursor when paginated', which is about mechanics rather than tool selection, so the agent gets no help choosing between this and the list/get siblings.

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