Skip to main content
Glama
thenavidm

Gumroad MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create product

create_product
Destructive

Add a new Gumroad product with name, price, and optional details like tags, category, and draft status. Requires explicit confirmation per call.

Instructions

Create product. Reviewed native POST /products; scope: edit_products. Requires explicit per-call confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes(required)
tagsNo(optional) array of tag strings
draftNo(optional, true or false, default false) save as an unpublished draft instead of publishing
priceYes(required) in the smallest currency unit (e.g. cents)
accountNoExact private profile label; never inherited credentials, ownership or scope proof.
confirmNoSet true only when the user asked for exactly this action.
categoryNo(optional) full category path from GET /v2/categories, e.g. "design/ui-and-web/figma"; cannot be sent with taxonomy_id
publishedNo(optional, true or false, default true) false saves as an unpublished draft, same as draft=true
descriptionNo(optional) HTML
native_typeNo(optional, "digital" (default), "course", "ebook", "membership", "bundle", "coffee", "call", or "commission") cannot be changed later
taxonomy_idNo(optional) numeric category ID; alias for category, cannot be sent with category
refund_periodNo(optional, "inherit", "none", "7", "14", "30", or "183") sets a product-level refund policy; "inherit" uses the account default. Only available when the account-level refund policy is not in effect; otherwise use PUT /v2/refund_policy
custom_summaryNo(optional)
custom_permalinkNo(optional)
refund_fine_printNo(optional) fine print for the product-level refund policy; requires refund_period unless the product already has one enabled, and cannot be combined with refund_period "inherit". Empty string clears it
customizable_priceNo(optional, true or false) pay-what-you-want
max_purchase_countNo(optional)
price_currency_typeNo(optional) ISO currency code; defaults to your account currency
subscription_durationNo(optional, membership only, "monthly", "quarterly", "biannually", "yearly", or "every_two_years")
suggested_price_centsNo(optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.0.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Explicit approval of this exact native effect or private file output."New value: +"Set true only when the user asked for exactly this action."
    • removedInput schema / properties / max_purchase_count / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / price / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / suggested_price_cents / maximum
      Removed value: -9007199254740991
  2. First observedv2.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower. The description still adds value by disclosing the required OAuth scope (edit_products) and the mandatory per-call confirmation requirement, which the annotations do not convey.

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 terse clauses, front-loaded with the action, and nothing wasted. "Reviewed native POST /products" is slightly cryptic but still informative rather than filler.

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 20-parameter creation tool with no output schema, the description is thin, though the annotations plus fully documented schema compensate heavily. It conveys scope and confirmation but says nothing about return behavior or side effects like product creation limits, leaving an agent to infer the rest.

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% with rich inline constraints (mutual exclusions, enums, defaults), so the schema carries the parameter burden. The description adds no parameter detail at all, making the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create product" is essentially a restatement of the tool name/title, so the core purpose is tautological. The added "native POST /products; scope: edit_products" pins the underlying endpoint and required scope, which is useful, but there is no differentiation from sibling creators like create_variant or create_offer_code.

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?

"Requires explicit per-call confirmation" gives a real usage rule (only invoke when the user asked for exactly this action), which is more than nothing. However, no alternatives are named and no when-not conditions are given beyond the confirmation gate.

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