Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Gumroad product details

gumroad_product_details_get
Read-onlyIdempotent

Fetch Gumroad product details, including files, bundles, previews, and creator reputation, by product URL, creator, or permalink.

Instructions

Get Gumroad product details: files, bundles, previews and creator reputation. Optional inputs: url, creator and permalink.

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_product_details_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA product URL, e.g. https://clifhuman.gumroad.com/l/latonc or https://gumroad.com/l/latonc.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
creatorNoGumroad 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.
permalinkNoProduct permalink, e.g. `latonc`.
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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the content scope (files, bundles, previews, reputation), which is useful but is closer to return-value information than behavior; nothing is said about failure modes, authentication, or the conversation_id sequencing the schema hints at.

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?

Two short sentences with the purpose front-loaded and no padding. The second sentence is arguably low value since the schema already marks those parameters optional, but it is not harmful.

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?

With no output schema, enumerating the returned data (files, bundles, previews, creator reputation) is a genuine contribution. However, the description omits the unusual required meta-parameters (context, llm_model) and the conversation_id sequencing requirement, which are the parts most likely to cause a misuse.

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 the schema already defines url, creator, permalink, context, llm_model and conversation_id in detail, including accepted URL forms and the 'unknown' fallback rule. The description only repeats which three parameters are optional and adds no format or selection meaning beyond that.

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 uses a specific verb and resource ('Get Gumroad product details') and enumerates what is returned: files, bundles, previews and creator reputation. It does not, however, distinguish this from the close sibling gumroad_product_get, so the boundary between the two is left to inference.

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?

The second sentence, 'Optional inputs: `url`, `creator` and `permalink`', is parameter guidance, not usage guidance. There is no statement of when to prefer this over gumroad_product_get or the various list siblings, and no prerequisites or exclusions.

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