Skip to main content
Glama

Submit a product

submit_product

Without sign-in, saves a private draft listing on Neeed Directory and returns a claim link: nothing is published or charged until the maker opens it, signs in and submits. Signed in with permission to edit listings, submits the listing to the maker's account: Neeed's automatic check publishes it or holds it for review, and Premium returns a Stripe Checkout link the maker pays in the browser.

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": {
      "website": "<website>",
      "name": "<name>",
      "punchline": "<punchline>",
      "description": "<description>",
      "category": "<category>",
      "product_type": "<product_type>",
      "pricing_model": "<pricing_model>"
    },
    "name": "submit_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe product's name
planNoThe plan the maker wants; nothing is charged until they submitfree
websiteYesThe product's website, https
categoryYesOne category slug from list_categories
punchlineYesOne line on what it does
descriptionYesWhat it does and for whom, factual, in plain text. The 1000-character limit counts &, < and > as several characters each
product_typeYessoftware, or digital_product for templates, courses, ebooks and the like
pricing_modelYesHow the maker charges for it

Output Schema

NameRequiredDescriptionDefault
urlNoThe listing: its public page when live or already_listed, its edit page otherwise
planNoSigned in only. pending_payment: Premium starts once the maker pays
slugNoThe reserved product slug for a draft
badgeNoThe Free plan, and a signed-in Premium submission until it is paid: the badge for the product's site, linking to its listing. html and markdown carry the light artwork
statusYesdraft_created: saved for the maker to claim. already_listed: the site is live on Neeed. already_submitted: signed in, this account already has a listing for the site, see listing_status. live: listed under the maker's account. in_review: saved to the maker's account, waiting on a review
claim_urlNoThe maker opens it, signs in and submits. Works once.
expires_atNoWhen the claim link stops working
next_stepsNo
checkout_urlNoSigned in, Premium, live: Stripe Checkout, which the maker opens and pays
listing_statusNoalready_submitted only: where that listing stands

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / badge / description
      Previous value: -"Free plan only: the badge for the product's site, linking to its future listing"New value: +"The Free plan, and a signed-in Premium submission until it is paid: the badge for the product's site, linking to its listing. html and markdown carry the light artwork"
    • addedOutput schema / properties / badge / properties / dark
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The same badge with the dark artwork",
      +  "properties": {
      +    "html": {
      +      "type": "string"
      +    },
      +    "markdown": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "html",
      +    "markdown"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / badge / required
      Previous value: -[
      -  "html",
      -  "markdown"
      -]New value: +[
      +  "html",
      +  "markdown",
      +  "dark"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing what actually happens: drafts are private, nothing is published or charged until the maker claims, an automatic check either publishes or holds for review, and Premium returns a Stripe Checkout link paid in-browser. These are non-obvious side effects and external dependencies an agent could not infer from the structured fields.

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 tightly packed sentences with the key constraint (nothing published or charged until claim) front-loaded and the mode branching clearly signposted. The semicolon-chained clauses are dense and could be split for faster scanning, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, high-stakes submission tool with auth-dependent branching, the definition covers modes, side effects, review behavior, and payment flow; with an output schema present it need not explain return values further. Nothing an agent needs in order to call or sequence it appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 earns an extra point by explaining the consequence of the plan parameter (Premium yields a Stripe Checkout link; nothing is charged until submit), which the schema only gestures at. It still does not clarify the draft-vs-submit distinction in terms of which parameters are required per mode.

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?

Names a specific verb (saves/submits) and resource (a product listing on Neeed Directory), and cleanly separates the two operating modes: anonymous draft plus claim link, versus signed-in submission into the maker's account. It does not distinguish itself from siblings like update_listing or upgrade_listing, so an agent must still 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 Guidelines4/5

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

The description effectively states the condition that selects each path (not signed in vs signed in with permission to edit listings), which is the main decision an agent faces. It never says when NOT to use it, e.g. that editing an existing listing should go to update_listing or that upgrading a plan goes to upgrade_listing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources