Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gumroad_get_product

Read-onlyIdempotent

Retrieve details for a single Gumroad product using its product ID and access token to inspect product data in your workflow.

Instructions

Get details for a single Gumroad product by ID.

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": {
      "access_token": "<access_token>",
      "product_id": "<product_id>"
    },
    "name": "gumroad_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct ID (permalink)
access_tokenYesGumroad access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.11
    • addedInput schema / properties / access_token
      Added value: +{
+  "description": "Gumroad access token",
+  "type": "string"
+}
    • removedInput schema / properties / api_key
      Removed value: -{
-  "description": "Gumroad access token",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "api_key",
-  "product_id"
-]New value: +[
+  "access_token",
+  "product_id"
+]
  2. Addedv0.1.9
  3. Removed
  4. Addedv0.1.5

TDQS

B3.4/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 and side-effect profile is fully covered without the description. The description adds no behavior beyond that, such as auth requirements, error behavior for unknown IDs, or rate limits, so it merits only the baseline-with-annotations score.

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?

A single front-loaded sentence with no wasted words; the resource and the selecting parameter are stated immediately.

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?

For a simple two-parameter read tool with full schema coverage, complete annotations, and no output schema, the description is sufficient to call it correctly. Only the shape of the returned product data and behavior on invalid IDs are unstated, which is a minor gap.

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%, and both parameters are documented in the schema, so the description need not compensate. It only echoes the ID-based lookup, adding no format, permalink-vs-numeric-ID distinctions, or token handling notes beyond the schema.

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 ('Get details'), a specific resource ('Gumroad product'), and the scope ('single ... by ID'), which implicitly separates it from gumroad_list_products. It does not name any sibling explicitly, 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?

There is no statement of when to use this versus gumroad_list_products or other Gumroad tools, and no prerequisites beyond the required token. Usage is only inferable from the phrase 'single product by ID'.

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