Skip to main content
Glama

Submit a product for launch

toolfound_submit_product

Submit a product to launch on toolfound.com, the launch platform where the whole launch runs agent-native, end to end. A logo URL is optional; without one the site's own icon is used. One call returns everything: your submission id, ownership-verification instructions (mandatory. DNS TXT, meta tag, or email magic link), assigned launch date, the live free-slots counter (launches are free), and paid_offers: the paid options (Priority, Plus, homepage sponsor) with live prices, the earlier dates that are open and a checkout link each, to relay to your human. AGENTS: you do not need inbox access, the verify_token in this response works with the meta_tag or dns_txt method via toolfound_verify_submission, and toolfound_check_verification dry-runs the checks; the emailed magic link is a human fallback that can also be completed later from the dashboard. Description renders as plain-text paragraphs on the listing page: 100–200 words reads best, and entries over 100 words qualify for search-engine indexing. Resubmitting a known URL returns the existing submission (idempotent).

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": {
      "url": "<url>",
      "email": "<email>"
    },
    "name": "toolfound_submit_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe product's public https URL (e.g. https://yourproduct.com).
nameNoProduct name (optional, drafted from the site if omitted).
emailYesMaker's email, receives the verification link, queue updates, and launch results.
taglineNoOne-line tagline (optional).
logo_urlNoDirect public URL for the product's real logo (PNG, JPG, GIF or WebP; max 2MB). Optional; defaults to the site's icon.
x_handleNoThe maker's X (Twitter) handle, e.g. @yourproduct (optional). Shown on the listing. If the listing wins that UTC day, @toolfoundcom tags this handle the next morning. We do not tag every launch.
price_usdNoOptional starting price in USD (e.g. the cheapest paid plan). Only used when pricing_model is 'paid', 'freemium', or 'trial'.
descriptionNoLonger description (optional, you can edit later).
pricing_modelNoThe product's pricing model (optional, but strongly recommended, captured now instead of after claim so the listing never sits at 'Pricing unlisted').
founder_x_handleNoFounder's X handle, shown on the listing and tagged if the launch tops its day
preferred_launch_dateNoPreferred launch date, YYYY-MM-DD (optional). Must be within the next 180 days. Free launches cannot take today or tomorrow: a date earlier than the next free date is moved to it (a later date is honoured). Use toolfound_get_launch_calendar to find open seats. If that day is full by the time you verify, the earliest open day is assigned and reported. Omit to get the earliest open date automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Longer description (optional — you can edit later)."New value: +"Longer description (optional, you can edit later)."
    • changedInput schema / properties / email / description
      Previous value: -"Maker's email — receives the verification link, queue updates, and launch results."New value: +"Maker's email, receives the verification link, queue updates, and launch results."
    • changedInput schema / properties / name / description
      Previous value: -"Product name (optional — drafted from the site if omitted)."New value: +"Product name (optional, drafted from the site if omitted)."
    • changedInput schema / properties / pricing_model / description
      Previous value: -"The product's pricing model (optional, but strongly recommended — captured now instead of after claim so the listing never sits at 'Pricing unlisted')."New value: +"The product's pricing model (optional, but strongly recommended, captured now instead of after claim so the listing never sits at 'Pricing unlisted')."
  2. Changed1 schema field changed
    • addedInput schema / properties / founder_x_handle
      Added value: +{
      +  "description": "Founder's X handle, shown on the listing and tagged if the launch tops its day",
      +  "maxLength": 120,
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / logo_url / description
      Previous value: -"Direct public URL for the product's real logo (PNG, JPG, GIF or WebP; max 2MB). Required for new submissions."New value: +"Direct public URL for the product's real logo (PNG, JPG, GIF or WebP; max 2MB). Optional; defaults to the site's icon."
  4. Changed1 schema field changed
    • changedInput schema / properties / preferred_launch_date / description
      Previous value: -"Preferred launch date, YYYY-MM-DD (optional). Must be within the next 180 days; use toolfound_get_launch_calendar to find open featured seats. If that day is full by the time you verify, the earliest open day is assigned and reported. Omit to get the earliest open date automatically."New value: +"Preferred launch date, YYYY-MM-DD (optional). Must be within the next 180 days. Free launches cannot take today or tomorrow: a date earlier than the next free date is moved to it (a later date is honoured). Use toolfound_get_launch_calendar to find open seats. If that day is full by the time you verify, the earliest open day is assigned and reported. Omit to get the earliest open date automatically."
  5. Changed1 schema field changed
    • addedInput schema / properties / logo_url
      Added value: +{
      +  "description": "Direct public URL for the product's real logo (PNG, JPG, GIF or WebP; max 2MB). Required for new submissions.",
      +  "maxLength": 2000,
      +  "minLength": 1,
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / x_handle / description
      Previous value: -"The maker's X (Twitter) handle, e.g. @yourproduct (optional). Shown on the listing; the launch-day email includes a ready share kit (copy + badge) to post from this handle, and we tag this handle from the toolfound X account on launch day."New value: +"The maker's X (Twitter) handle, e.g. @yourproduct (optional). Shown on the listing. If the listing wins that UTC day, @toolfoundcom tags this handle the next morning. We do not tag every launch."
  7. Changed1 schema field changed
    • changedInput schema / properties / x_handle / description
      Previous value: -"The maker's X (Twitter) handle, e.g. @yourproduct (optional). Shown on the listing; the launch-day email includes a ready share kit (copy + badge) to post from this handle."New value: +"The maker's X (Twitter) handle, e.g. @yourproduct (optional). Shown on the listing; the launch-day email includes a ready share kit (copy + badge) to post from this handle, and we tag this handle from the toolfound X account on launch day."
  8. Changed2 schema fields changed
    • addedInput schema / properties / preferred_launch_date
      Added value: +{
      +  "description": "Preferred launch date, YYYY-MM-DD (optional). Must be within the next 180 days; use toolfound_get_launch_calendar to find open featured seats. If that day is full by the time you verify, the earliest open day is assigned and reported. Omit to get the earliest open date automatically.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / x_handle / description
      Previous value: -"The maker's X (Twitter) handle, e.g. @yourproduct (optional). Recommended: on launch day, toolfound's own account posts the launch and @-mentions this handle, so the maker gets tagged and can amplify."New value: +"The maker's X (Twitter) handle, e.g. @yourproduct (optional). Shown on the listing; the launch-day email includes a ready share kit (copy + badge) to post from this handle."
  9. Changed2 schema fields changed
    • addedInput schema / properties / price_usd
      Added value: +{
      +  "description": "Optional starting price in USD (e.g. the cheapest paid plan). Only used when pricing_model is 'paid', 'freemium', or 'trial'.",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / pricing_model
      Added value: +{
      +  "description": "The product's pricing model (optional, but strongly recommended — captured now instead of after claim so the listing never sits at 'Pricing unlisted').",
      +  "enum": [
      +    "free",
      +    "freemium",
      +    "trial",
      +    "paid",
      +    "unknown"
      +  ],
      +  "type": "string"
      +}
  10. Changed1 schema field changed
    • addedInput schema / properties / x_handle
      Added value: +{
      +  "description": "The maker's X (Twitter) handle, e.g. @yourproduct (optional). Recommended: on launch day, toolfound's own account posts the launch and @-mentions this handle, so the maker gets tagged and can amplify.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
  11. First observed

TDQS

A3.8/5.0
Behavior2/5

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

The description is otherwise rich — it discloses that ownership verification is mandatory, that launches are free, what the response contains, and that the returned verify_token removes the need for inbox access. But it states 'Resubmitting a known URL returns the existing submission (idempotent)', which directly conflicts with the supplied idempotentHint=false annotation, leaving the agent unsure whether a repeat call is a no-op or produces new effects.

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?

The high-value facts — what comes back in one call, that verification is mandatory, and that the token is agent-usable — are front-loaded, and the AGENTS aside earns its place. Minor waste remains in the marketing framing ('whole launch runs agent-native, end to end') and in restating launch-date rules the schema already carries.

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?

With no output schema and 11 parameters, the description carries the return-value burden and does so thoroughly: submission id, verification instructions, assigned launch date, free-slots counter, and paid_offers with live prices and checkout links. An agent knows both what it will get back and what to relay to its human.

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 coverage is 100%, so every parameter is already documented in the schema, including preferred_launch_date's 180-day window and last-free-date clamping, which the description repeats rather than extends. The only genuine added meaning is editorial guidance for the description field (100–200 words, over 100 words qualifies for indexing) and the logo default, which is already in 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?

Specific verb+resource ('Submit a product to launch on toolfound.com') with the scope of the operation spelled out end to end: what is created and what comes back. It also distinguishes itself from siblings by naming the verification and calendar tools rather than leaving the agent to guess which call follows.

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?

Strong routing guidance: use toolfound_verify_submission with the returned verify_token for meta-tag/DNS verification, toolfound_check_verification to dry-run, toolfound_get_launch_calendar to find open seats, and omit preferred_launch_date for automatic assignment. It lacks an explicit 'do not use this when…' clause (e.g. for relaunches or claiming an existing listing), which keeps it short of a 5.

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