Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Gumroad search suggestions

gumroad_search_suggestions_list
Read-onlyIdempotent

Fetches Gumroad product autocomplete suggestions for a search query, or returns trending products when the query is empty.

Instructions

Get Gumroad's autocomplete product suggestions, or trending products for an empty query. Optional inputs: query. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "gumroad_search_suggestions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoText to autocomplete. Empty or omitted returns Gumroad's trending products.
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.
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.6/5.0
Behavior3/5

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

The annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds the empty-query fallback to trending products, but does not discuss authentication, rate limits, or result ordering.

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

Conciseness5/5

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

The description is two short sentences with the core behavior front-loaded and no unnecessary wording. It is appropriately sized for a simple autocomplete/list tool.

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?

Given the rich annotations, full schema descriptions, and simple list-returning behavior, the description is nearly complete. The only minor gap is that it says only 'Returns a list' without indicating the shape or ordering of results.

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 query, context, llm_model, and conversation_id. The description reinforces the empty-query behavior for query but does not add meaning beyond the schema, and it does not mention the required context and llm_model parameters.

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: getting Gumroad autocomplete product suggestions, with a clear fallback to trending products for an empty query. It is distinguishable from generic search tools, though it does not explicitly name sibling alternatives.

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 gives one useful usage condition: an empty or omitted query returns trending products. However, it does not explain when to choose this tool over related search tools such as gumroad_products_search or gumroad_tags_search.

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