Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Gumroad related products

gumroad_product_related_list
Read-onlyIdempotent

Lists products bought together with specified Gumroad products, helping identify cross-sell and bundling opportunities from product IDs.

Instructions

List products bought together with Gumroad products. Requires productIds. 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": {
      "productIds": "<productIds>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "gumroad_product_related_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many related products to return, 1 to 100. Default: 20.
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.
productIdsYesRequired. One to ten product ids, comma-separated or repeated.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only 'Returns a list', which is near-trivial and says nothing about ordering, result size, or whether an empty list is possible. With no output schema present, more return-shape context would have been valuable.

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 purpose and the required input, with no filler. The final 'Returns a list' sentence is borderline redundant but does hint at the response shape in the absence of an output schema.

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 simple read-only listing tool with fully documented parameters and annotations covering safety, this is minimally adequate. It leaves the notion of 'related' (bought together) unexplained beyond the opening clause and gives no sense of result ordering or cardinality, which a richer description would have supplied.

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 coverage is 100% and every parameter (including limit, context, llm_model, conversation_id) is documented in the schema. The description only restates that productIds is required, adding no meaning beyond the structured fields — the baseline 3 for full coverage 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 gives a specific verb and resource — 'List products bought together with Gumroad products' — which conveys the co-purchase/related semantics an agent needs. It does not name any sibling (e.g. gumroad_product_reviews_list or gumroad_product_details_get) to sharpen the distinction, so it stops short of a 5.

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?

'Requires `productIds`' states a prerequisite but not when to choose this tool over product details, reviews, or search. There is no when-to-use context and no exclusion of alternatives.

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