Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Gumroad product

gumroad_product_get
Read-onlyIdempotent

Retrieve Gumroad product details, including price, ratings, tiers, covers, attributes, refund policy, and reviews, by product URL, creator username, or permalink.

Instructions

Get Gumroad product: price, ratings, tiers, covers, attributes, refund policy and reviews. 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_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=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description's only real contribution is enumerating the returned data fields, which matters because no output schema exists, but it says nothing about partial-field availability, error behavior for invalid slugs, or the interaction of the three identifier inputs.

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, field list front-loaded after the verb-and-resource statement, with no filler or marketing language. The 'Optional inputs' clause is the weakest part since it duplicates schema information rather than adding guidance.

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 read-only fetch tool with rich annotations but no output schema, the field enumeration is a reasonable stand-in for return-value documentation. However, an agent still cannot tell from the description how this differs from gumroad_product_details_get, nor how the required context/llm_model/conversation_id protocol constrains calling it.

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 documents all six parameters thoroughly, including examples for url, creator and permalink. The description adds no meaning beyond restating three of them, and it omits mention of the required context/llm_model parameters and the conversation_id echo protocol.

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 ('Get Gumroad product') and enumerates the returned data (price, ratings, tiers, covers, attributes, refund policy, reviews), which tells an agent what to expect. It does not distinguish itself from the sibling 'gumroad_product_details_get', and the mention of 'reviews' overlaps with 'gumroad_product_reviews_list', leaving some ambiguity about which call to make.

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 explicit when-to-use or when-not-to-use guidance, and no routing to the many siblings that fetch overlapping product data (details_get, reviews_list, related_list). The 'Optional inputs' line names identifiers but never says how to choose between url, creator, and permalink, or what happens if several are supplied.

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