Skip to main content
Glama

PebbleLaunch

Submit a product to PebbleLaunch

submit_product

Submit the user's own product for a free launch day on PebbleLaunch. Only submit products the user owns and has asked you to list. Returns an id, a one-time status_key (save it) and ownership-proof options. Next: add ONE proof on the product's domain (a .well-known file, a meta tag, or a DNS TXT record), then call check_status. The maker then confirms by email; nothing is listed before a human confirms. Rules: https://pebblelaunch.com/rules.

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>",
      "tagline": "<tagline>",
      "description": "<description>",
      "url": "<url>",
      "categories": "<categories>",
      "pricing": "<pricing>",
      "maker_name": "<maker_name>",
      "maker_email": "<maker_email>"
    },
    "name": "submit_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps:// product URL on the maker's own domain
nameYesProduct name, ≤40 chars
pricingYes
taglineYes≤60 chars, plain text, no links
logo_urlNo
categoriesYes
maker_nameYesPerson or company shown as maker
descriptionYes≤600 chars, plain text, no links; claims must match the site
maker_emailYesThe maker's email; we send ONE confirmation link to it. Never shown publicly.
screenshotsNo
preferred_dateNoOptional UTC day YYYY-MM-DD, tomorrow or later

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare non-readOnly, openWorld and non-destructive; the description adds the substantive behavior beyond them — that the response includes an id and a one-time status_key that must be saved, that ownership proof on the maker's domain is mandatory, and that nothing is listed until a human confirms. That is exactly the information an agent needs before triggering a write with a public-facing consequence.

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 dense sentences, each doing distinct work: purpose, ownership constraint, return payload, required proof-then-check workflow, human gate. Purpose and constraints are front-loaded and there is no filler or restatement of the name.

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 mutation tool with no output schema, the description explains the return payload, the mandatory verification ritual, and the human-in-the-loop gate, which is most of what an agent needs. The remaining gap is submission-time field guidance for the undocumented parameters, though the rules link offers a fallback.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 11 parameters at 64% schema coverage, four fields (logo_url, screenshots, pricing, categories) carry no schema description, and the description does not compensate — it never mentions character limits, category selection, or the optional preferred_date. The only parameter-adjacent hint is that the URL must live on the maker's own domain, which the schema already states.

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 — submit the user's own product for a free launch day on PebbleLaunch — and separates itself from the read-side siblings by naming check_status as the follow-up tool. An agent can distinguish this submission action from get_launch/list_launches without opening any schema.

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 an explicit eligibility gate ('Only submit products the user owns and has asked you to list') and a complete next-step chain: add exactly ONE domain proof, then call check_status. The workflow ordering leaves nothing to inference, and the human email confirmation is flagged as a hard precondition.

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