Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Gumroad creator

gumroad_creator_get
Read-onlyIdempotent

Fetch a Gumroad creator's public profile, including name, bio, avatar, socials, reputation, tabs, and sections, by supplying a username or profile URL.

Instructions

Get a Gumroad creator's public profile: name, bio, avatar, socials, reputation, tabs and sections. Requires creator.

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": {
      "creator": "<creator>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "gumroad_creator_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
creatorYesRequired. Gumroad 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.
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, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds the concrete list of returned fields, which is useful given there is no output schema, but it says nothing about pagination, error behavior, or privacy limits on the profile data.

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?

Placeholder

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?

Placeholder

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 fully documents all four parameters, including the creator username format and the meta-parameters (context, llm_model, conversation_id). The description only restates that `creator` is required, adding no syntax or format detail 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?

The description uses a specific verb ('Get') with a clearly bounded resource ('a Gumroad creator's public profile') and enumerates what the profile contains (name, bio, avatar, socials, reputation, tabs, sections). It does not distinguish itself from potential siblings like stan_store_creator_get or behance_profile_get, so it falls 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?

Placeholder

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