neuron

Create Product

neuron_create_product

Create a digital product/service with a public checkout link. Amount in kobo (minor units): ₦1 = 100. Minimum ₦500 = 50000. For 'file' delivery, upload the file first (neuron_upload_media) and pass its URL as deliveryFileUrl. On payment, Neuron confirms it and delivers the product to the buyer's WhatsApp automatically.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Short label e.g. 'E-book', 'Presets', 'Service'
`codes`	No	For codeMode 'pool': the unique codes/keys to add (one gets sent per buyer). Appended to any existing pool.
`theme`	No	Per-product theme: { bg, accent, text (hex), mode: 'light'\|'dark', layout: 'hero'\|'side', coverAspect: '16/10'\|'3/2'\|'1/1'\|'4/5', cta: buy-button label e.g. 'Reserve your hour' }
`title`	Yes	Product title shown to buyers
`content`	No	Rich product-page content blocks. Ordered array of {type, ...}: heading {text,level}, text {markdown}, image {url,caption}, video {url}, callout {emoji,text}, collapsible {title,blocks[]}, divider {}, button {label,url}, embed {url}, spacer {}
`enabled`	No	Whether the product is live
`category`	No	Category label e.g. 'Productivity'
`codeMode`	No	For deliveryType 'code': 'shared' (same text to every buyer), 'pool' (a unique code per sale from codes you upload — sells out when empty), or 'generated' (auto-mint a unique license key per sale)
`currency`	No	ISO currency (default NGN)
`feePayer`	No	'buyer' (fee added on top, seller gets full price — default) or 'seller' (fee deducted)
`channelId`	No	WhatsApp session UUID used to deliver the product (defaults to the org default channel)
`coverType`	No	How the cover renders
`coverColor`	No	Cover colour (hex) for 'color'/'gradient' cover types
`coverEmoji`	No	Emoji used as a cover fallback (e.g. 📓)
`membership`	No	Make this a recurring subscription/membership: it tracks a paid period per buyer, renews from their Neuron wallet when possible (else emails a reminder — no card auto-charge), and marks them lapsed when the period + grace passes. React to membership.started/renewed/lapsed in Flows to deliver whatever the membership grants.
`priceMinor`	Yes	Current price (charged). Amount in kobo (minor units): ₦1 = 100. Minimum ₦500 = 50000. Set 0 for a free product (no payment).
`coverColor2`	No	Second colour (hex) for 'gradient' cover
`description`	No	Rich description / what the buyer gets
`deliveryText`	No	For 'link'/'code': the link or code the buyer receives. Optional note for 'file'.
`deliveryType`	Yes	How the product is delivered: 'file' (uploaded file), 'link' (URL), or 'code' (text/code)
`coverImageUrl`	No	Cover image URL
`checkoutFields`	No	Custom checkout questions the buyer answers (name, address, specs/customisations…). Their answers are attached to the order and sent to the seller.
`deliveryFileUrl`	No	For deliveryType 'file': the uploaded file URL (upload first with neuron_upload_media)
`deliveryFileName`	No	Filename shown in the WhatsApp document
`membershipInterval`	No	Billing period. Required when membership is true.
`originalPriceMinor`	No	Optional compare-at / 'was' price (kobo), shown struck through. Must be ≥ current price.
`membershipGraceDays`	No	Days after the period ends before an unpaid member lapses (and, if a group is attached, is removed from it). Default 1.
`membershipGroupName`	No	Group subject used when the attached group is auto-created (defaults to the product title). Only relevant with membershipGroupSlug.
`membershipGroupSlug`	No	OPTIONAL: attach a WhatsApp group as a membership perk. Org-unique handle (lowercase letters, numbers, hyphens); the group is created on the first sale, buyers are added on renewal and removed on lapse. Your connected number must be a group admin. Omit for a membership that isn't group-based.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed5 schema fields changedSep 3, 2026

addedInput schema / properties / membership

Added value: +{
+  "description": "Make this a recurring subscription/membership: it tracks a paid period per buyer, renews from their Neuron wallet when possible (else emails a reminder — no card auto-charge), and marks them lapsed when the period + grace passes. React to membership.started/renewed/lapsed in Flows to deliver whatever the membership grants.",
+  "type": "boolean"
+}

addedInput schema / properties / membershipGraceDays

Added value: +{
+  "description": "Days after the period ends before an unpaid member lapses (and, if a group is attached, is removed from it). Default 1.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / membershipGroupName

Added value: +{
+  "description": "Group subject used when the attached group is auto-created (defaults to the product title). Only relevant with membershipGroupSlug.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / membershipGroupSlug

Added value: +{
+  "description": "OPTIONAL: attach a WhatsApp group as a membership perk. Org-unique handle (lowercase letters, numbers, hyphens); the group is created on the first sale, buyers are added on renewal and removed on lapse. Your connected number must be a group admin. Omit for a membership that isn't group-based.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / membershipInterval

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "daily",
+        "weekly",
+        "monthly"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Billing period. Required when membership is true."
+}

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / theme / description

Previous value: -"Per-product theme: { bg, accent, text (hex), mode: 'light'|'dark', layout: 'hero'|'side', coverAspect: '16/10'|'3/2'|'1/1'|'4/5' }"New value: +"Per-product theme: { bg, accent, text (hex), mode: 'light'|'dark', layout: 'hero'|'side', coverAspect: '16/10'|'3/2'|'1/1'|'4/5', cta: buy-button label e.g. 'Reserve your hour' }"

Changed5 schema fields changedAug 31, 2026

addedInput schema / properties / checkoutFields

Added value: +{
+  "description": "Custom checkout questions the buyer answers (name, address, specs/customisations…). Their answers are attached to the order and sent to the seller.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "key": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "options": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "placeholder": {
+        "type": "string"
+      },
+      "required": {
+        "type": "boolean"
+      },
+      "type": {
+        "enum": [
+          "text",
+          "textarea",
+          "number",
+          "email",
+          "phone",
+          "select"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "key",
+      "label",
+      "type"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / properties / coverType / enum

Previous value: -[
-  "emoji",
-  "image",
-  "color",
-  "gradient"
-]New value: +[
+  "none",
+  "emoji",
+  "image",
+  "color",
+  "gradient"
+]

addedInput schema / properties / originalPriceMinor

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Optional compare-at / 'was' price (kobo), shown struck through. Must be ≥ current price."
+}

changedInput schema / properties / priceMinor / description

Previous value: -"Price. Amount in kobo (minor units): ₦1 = 100. Minimum ₦500 = 50000."New value: +"Current price (charged). Amount in kobo (minor units): ₦1 = 100. Minimum ₦500 = 50000. Set 0 for a free product (no payment)."

changedInput schema / properties / theme / description

Previous value: -"Per-product theme: { bg, accent, text, mode: 'light'|'dark' } (hex colours)"New value: +"Per-product theme: { bg, accent, text (hex), mode: 'light'|'dark', layout: 'hero'|'side', coverAspect: '16/10'|'3/2'|'1/1'|'4/5' }"

Changed5 schema fields changedAug 31, 2026

addedInput schema / properties / content

Added value: +{
+  "description": "Rich product-page content blocks. Ordered array of {type, ...}: heading {text,level}, text {markdown}, image {url,caption}, video {url}, callout {emoji,text}, collapsible {title,blocks[]}, divider {}, button {label,url}, embed {url}, spacer {}",
+  "type": "array"
+}

addedInput schema / properties / coverColor

Added value: +{
+  "description": "Cover colour (hex) for 'color'/'gradient' cover types",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / coverColor2

Added value: +{
+  "description": "Second colour (hex) for 'gradient' cover",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / coverType

Added value: +{
+  "description": "How the cover renders",
+  "enum": [
+    "emoji",
+    "image",
+    "color",
+    "gradient"
+  ],
+  "type": "string"
+}

addedInput schema / properties / theme

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Per-product theme: { bg, accent, text, mode: 'light'|'dark' } (hex colours)",
+  "type": "object"
+}

AddedAug 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations are all false hints, so the description carries the burden — and it delivers: it discloses a public checkout link, the kobo/minimum-price rule, and a significant autonomous side effect ('On payment, Neuron confirms it and delivers the product to the buyer's WhatsApp automatically'). No contradiction with annotations, though it omits storefront listing exposure and response contents.

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?

Four sentences with zero filler. The core purpose is front-loaded, followed by the unit constraint, the file-upload prerequisite, and the post-payment delivery behavior — every sentence earns its place despite the tool's 29-parameter complexity.

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 29-parameter tool with nested objects and enums, the 100%-covered schema does the heavy lifting. The description adds the essential runtime behavior — automatic WhatsApp delivery, currency units, minimum price, and the upload prerequisite — that the schema alone doesn't highlight. It doesn't state what the tool returns (no output schema exists), 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%, so the baseline is 3. The description reinforces priceMinor (kobo, minimum ₦500 = 50000) and deliveryFileUrl (upload-first flow), but both facts already exist verbatim in the schema's parameter descriptions, so the description adds emphasis rather than new semantic meaning.

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

Purpose5/5

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

States a specific verb+resource: 'Create a digital product/service with a public checkout link.' The 'public checkout link' detail clarifies the product scope, and the 'Create' verb immediately differentiates it from siblings like neuron_update_product, neuron_delete_product, and neuron_duplicate_product.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete workflow guidance for the 'file' delivery path: 'upload the file first (neuron_upload_media) and pass its URL as deliveryFileUrl', naming the prerequisite sibling tool explicitly. It doesn't spell out when to prefer this over neuron_update_product or neuron_add_product_codes, but the create-versus-update context is clear and the upload prerequisite is actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All neuron tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation3/5

Most tools are clearly separated by resource type, but there is meaningful overlap in messaging entry points (send_message, send_whatsapp, compose_message, bot_api_send) and contact ingestion/sync tools (import_contacts, populate_contacts, sync_whatsapp_contacts). The descriptions help disambiguate, but with 309 tools an agent will frequently need to read closely to pick the right one.

Naming Consistency4/5

The overwhelming majority of tools follow a consistent verb_noun snake_case pattern: create_*, get_*, list_*, update_*, delete_*. Minor deviations like sales_stats, lead_stats, wallet_balance, and whoami break the pattern slightly, but overall naming is highly predictable.

Tool Count1/5

309 tools is an extreme count for any MCP server, even a broad platform. This creates significant cognitive load and navigation overhead for agents, and far exceeds the well-scoped 3-15 tool range where coherence is strongest.

Completeness4/5

The tool surface is remarkably comprehensive across bots, contacts, campaigns, flows, knowledge bases, personas, marketplace, wallet, and products. Minor gaps exist — lead sources lack update/delete tools, and there is no single get_task or get_webhook alongside their list/update/delete counterparts — but these are workable gaps rather than dead ends.

Resources

Need Help?