Skip to main content
Glama

Submit a product to the directory

submit_product

Add a product to the directory on behalf of the builder whose agent token this call carries. Call this when the person you are working for has asked to be listed here, or has asked you to add a product they built. Do not call it to add somebody else's product, and do not call it speculatively — a listing is a public claim about a real builder. REQUIRES A TOKEN: send Authorization: Bearer wayb_…. A builder creates one at /mine while signed in; without it this tool refuses and every other tool here still works. The listing is created as PENDING and is reviewed before it appears — a successful call returns an id and a status of "pending", never a live listing. Do not report it as published. Submit the builder's OWN product. A builder can list more than one product, but the directory refuses a second copy of a product it already lists (by website host or by name) with a message saying so. Call list_filters first: category and region are closed vocabularies, listed in full under products.accepted_values, and a value outside them is rejected rather than corrected. Funding fields are optional and tri-state — omit activelyRaising, or send null, where the builder has not said. Do not infer it, and do not send false to mean "did not say".

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": {
      "name": "<name>",
      "oneLiner": "<oneLiner>",
      "description": "<description>",
      "websiteUrl": "<websiteUrl>",
      "logoUrl": "<logoUrl>",
      "screenshots": "<screenshots>",
      "category": "<category>",
      "region": "<region>",
      "fundingStage": "<fundingStage>"
    },
    "name": "submit_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
mrrNoMonthly recurring revenue, only where the builder chose to publish it.
cityNoCity, or null.
nameYesThe product name, up to 80 characters.
openToNoWhat the builder invited contact about. Omit for none.
regionYesREQUIRED. Country name from products.accepted_values.regions in list_filters (the full list; products.regions only names countries that already have listings). Closed vocabulary. Use "Global" where the builder is not anywhere in particular or would rather not say — that is a real answer on this list, and it is the one to send rather than guessing a country or omitting the field.
builderNoAttribution: `name` is required inside it, the rest is optional. REQUIRED on the first listing from this account. Leave it out on later ones and the builder details from the account's newest listing are used; send it only when the builder wants them changed. Every listing from one account shares one builder page however this is filled in.
logoUrlYesREQUIRED. The product's square logo: an https link to a PNG, JPEG or WebP (up to 2MB, under 4000×4000), or a base64 `data:image/...` URL. The directory fetches it, checks it is a real image, and stores its own re-encoded copy; send the image file itself, not a page that shows it. Prefer links: a whole request is capped at 256KB, so data URLs only suit small images. Ask the builder for their logo rather than picking an image off their site.
socialsNoThe PRODUCT's own accounts, keyed by platform — not the builder's, which go under `builder.socials`. Keys: `x`, `linkedin`, `instagram`, `tiktok`, `youtube`, `facebook`, `github`, `email`. Each is `{ "url": "…" }` except `x`, which is `{ "handle": "…" }`, and `email`, which is `{ "address": "…" }` and should be a business address (support@, hello@) rather than a person's. `github` is the PRODUCT's repository — the code somebody would clone. The builder's own GitHub account is a different thing and goes in `builder.socials.github`.
categoryYesREQUIRED. The product's MAIN category, from products.accepted_values.categories in list_filters. Closed vocabulary. This is the one a row, a card and the sharing image show.
oneLinerYesOne sentence saying what it does, up to 80 characters. Not a tagline.
categoriesNoOptional. Up to 3 categories from list_filters, MAIN FIRST — for a product that is honestly more than one thing (an AI agent that is also a dev tool). The first must be the same value as `category`; send it first or leave it out of the list and it is put there. A listing is findable and filed under all of them, so send only the ones the builder would claim: three loosely-related categories are worse for them than one true one. Ask the builder rather than inferring from their site.
websiteUrlYesREQUIRED. The product's own https URL — the address a reader opens. A code repository or an app store page counts. REFUSED: a shared document (Drive, Docs, Dropbox, Notion), and a free platform deploy subdomain (vercel.app, netlify.app, github.io, web.app, railway.app and the like) — the builder needs a domain of their own first. Never invent one: ask the builder.
descriptionYesREQUIRED, up to 800 characters. A short paragraph in the builder's OWN words about what the product is and who it is for, shown on the listing's own page. Plain text — links are not rendered, so put the address in websiteUrl. Never write it yourself, and never pad it to a length: ask the builder for it, the way you would ask for the URL. A short answer in their words is worth more here than a long one in yours. It became required on 2026-09-03 because a listing without one has nothing on its page a search engine can tell apart from every other listing.
screenshotsYesREQUIRED, 1 to 4. Screenshots of the product, each an https link to a PNG, JPEG or WebP (up to 2MB) or a base64 data URL, copied in like logoUrl. Ask the builder for them.
fundingStageYesFunding stage. Use "undisclosed" where the builder has not said — never guess.
activelyRaisingNotrue, false, or null for "would rather not say". Default null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / builder / description
      Previous value: -"Attribution. `name` is required; the rest is optional."New value: +"Attribution: `name` is required inside it, the rest is optional. REQUIRED on the first listing from this account. Leave it out on later ones and the builder details from the account's newest listing are used; send it only when the builder wants them changed. Every listing from one account shares one builder page however this is filled in."
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "oneLiner",
      -  "description",
      -  "websiteUrl",
      -  "logoUrl",
      -  "screenshots",
      -  "category",
      -  "region",
      -  "fundingStage",
      -  "builder"
      -]New value: +[
      +  "name",
      +  "oneLiner",
      +  "description",
      +  "websiteUrl",
      +  "logoUrl",
      +  "screenshots",
      +  "category",
      +  "region",
      +  "fundingStage"
      +]
  2. Changed6 schema fields changed
    • addedInput schema / properties / builder / properties / avatarUrl / description
      Added value: +"Optional. The builder's photo, sent like logoUrl (an image link or data URL) and copied in. Without one the site borrows their X, GitHub or Gravatar picture."
    • changedInput schema / properties / category / description
      Previous value: -"REQUIRED. The product's MAIN category, from list_filters. Closed vocabulary. This is the one a row, a card and the sharing image show."New value: +"REQUIRED. The product's MAIN category, from products.accepted_values.categories in list_filters. Closed vocabulary. This is the one a row, a card and the sharing image show."
    • changedInput schema / properties / logoUrl / description
      Previous value: -"An https URL to a square logo, or null."New value: +"REQUIRED. The product's square logo: an https link to a PNG, JPEG or WebP (up to 2MB, under 4000×4000), or a base64 `data:image/...` URL. The directory fetches it, checks it is a real image, and stores its own re-encoded copy; send the image file itself, not a page that shows it. Prefer links: a whole request is capped at 256KB, so data URLs only suit small images. Ask the builder for their logo rather than picking an image off their site."
    • changedInput schema / properties / region / description
      Previous value: -"REQUIRED. Country name from list_filters. Closed vocabulary. Use \"Global\" where the builder is not anywhere in particular or would rather not say — that is a real answer on this list, and it is the one to send rather than guessing a country or omitting the field."New value: +"REQUIRED. Country name from products.accepted_values.regions in list_filters (the full list; products.regions only names countries that already have listings). Closed vocabulary. Use \"Global\" where the builder is not anywhere in particular or would rather not say — that is a real answer on this list, and it is the one to send rather than guessing a country or omitting the field."
    • addedInput schema / properties / screenshots
      Added value: +{
      +  "description": "REQUIRED, 1 to 4. Screenshots of the product, each an https link to a PNG, JPEG or WebP (up to 2MB) or a base64 data URL, copied in like logoUrl. Ask the builder for them.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 4,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "oneLiner",
      -  "description",
      -  "websiteUrl",
      -  "category",
      -  "region",
      -  "fundingStage",
      -  "builder"
      -]New value: +[
      +  "name",
      +  "oneLiner",
      +  "description",
      +  "websiteUrl",
      +  "logoUrl",
      +  "screenshots",
      +  "category",
      +  "region",
      +  "fundingStage",
      +  "builder"
      +]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations it discloses auth requirements (Bearer wayb_ token, source at /mine), the pending-review lifecycle and that the return is an id plus status "pending" rather than a live listing, and duplicate rejection by website host or name. These are exactly the behavioral facts annotations cannot convey. It stops short of detailing rate limits or error shapes, so not a 5.

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?

Dense and front-loaded with purpose before constraints, and nearly every sentence carries a distinct rule. Some redundancy exists ("Submit the builder's OWN product" restates the earlier exclusion) and the single unbroken block makes the auth/prerequisite guidance harder to scan.

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 a 16-parameter, 9-required mutation tool with nested objects and no output schema, the description covers auth, prerequisites, lifecycle, duplicate handling, vocabulary constraints, and the successful return value. An agent has everything needed to call it correctly and report the result honestly.

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 coverage is already 100%, so the baseline is 3, but the description adds real meaning: closed vocabularies must be read from list_filters, region should be "Global" rather than guessed, and the funding tri-state semantics (omit or null vs. false) are spelled out. It reinforces rather than duplicates the schema.

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 and resource ("Add a product to the directory") plus the scoping constraint that it acts on behalf of the token's builder. It is immediately distinguishable from siblings like list_filters and search_products.

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

Usage Guidelines5/5

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

Gives explicit when-to-use triggers, explicit when-not-to (somebody else's product, speculative listings), and names a required prerequisite call to list_filters before submitting. The alternative/ordering guidance is unambiguous.

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