Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Gumroad post

gumroad_post_get
Read-onlyIdempotent

Fetch a Gumroad post's HTML body, comment settings, and recent posts by URL, creator, or slug. Use it to retrieve full post content and context for analysis or summaries.

Instructions

Get a Gumroad post with its HTML body, comments setting and recent posts. Optional inputs: url, creator and slug.

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

Input Schema

NameRequiredDescriptionDefault
urlNoA post URL, e.g. https://clifhuman.gumroad.com/p/some-post.
slugNoPost slug, e.g. `some-post`.
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.
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 covered. The description usefully adds the return contents, but says nothing about authentication, rate limits, or the failure behavior when a post cannot be resolved.

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 primary action and the returned fields front-loaded; nothing is padded. The trailing 'Optional inputs' list is slightly redundant given the schema but stays compact.

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, the description does well to enumerate the returned fields. However, for a six-parameter tool with a required conversation_id handshake and analytics parameters, it leaves the routing and sequencing guidance entirely to the schema.

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%, so all six parameters are already documented in detail. The description only restates that url, creator and slug are optional, adding no format or precedence rules beyond the schema, which is the expected baseline of 3.

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 a Gumroad post') and names what the response contains (HTML body, comments setting, recent posts). It does not distinguish this from siblings such as gumroad_creator_posts_list or gumroad_post_comments_list, so an agent must infer the boundary.

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 named alternative. The phrase 'Optional inputs: url, creator and slug' hints that several identifiers are accepted but never explains which to prefer or when this tool beats the sibling list tools.

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