Zero to Hundred marketplace

Create a Zero to Hundred draft listing

z2h_create_draft_listing

Destructive

Create an invisible draft and return editUrl and publishUrl. Price and source inclusion are Builder decisions. Set sourceCodeIncluded only after confirmation; omitted values default to false. Requires listings:write. Returns the draft identity and web edit/review links. Check z2h_list_my_listings before retrying, because creation is not idempotent. Source delivery, review and publishing continue in the web wizard.

Input Schema

TableJSON Schema

Name	Required	Description
`faqs`	No	Supplying FAQs disables the automatic FAQ draft.
`type`	Yes	Software category that best matches its main use.
`title`	Yes	Name Buyers will see on the software listing.
`demoUrl`	No	Public HTTP or HTTPS demo URL. Omit when no demo is available.
`domains`	No	Industry tags for the software. Choose keys from the Zero to Hundred taxonomy: ai, analytics, art-design, auth-identity, cms, conference, developer-tools, devops, e-commerce-marketplace, education, entertainment, environmental, fashion, finance, food, gaming, graphic-design, health, interior-design, marketing, membership, messaging, non-profit, political, productivity, real-estate, religious, services, social, technology, travel, ux-ui, wedding, other. Omission creates a draft without industry tags.
`imageUrls`	No	HTTP or HTTPS screenshot URLs. The first image becomes the thumbnail.
`techStack`	No	Frameworks and languages used by the software.
`askingPrice`	No	USD license price confirmed by the Builder. Omit if undecided.
`thumbnailUrl`	No	HTTP or HTTPS image URL for the marketplace thumbnail.
`sourceRepoUrl`	No	GitHub repository URL. Connecting and verifying source continues in the web wizard.
`videoUploadUrl`	No	A YouTube or Loom demo URL.
`longDescription`	Yes	What the software does, who it helps, and what the Buyer receives.
`operatingStatus`	Yes	State of the software itself, independent of the listing publication status.
`maintenanceLevel`	No	Maintenance commitment the Builder offers.
`shortDescription`	Yes	Buyer-facing summary shown on marketplace cards.
`documentationLevel`	No	Documentation supplied with the software.
`sourceCodeIncluded`	No	Whether the sale includes source code. Omission records false. Set true only after the Builder confirms that source code is included.
`associatedListingIds`	No	IDs of related listings owned by this Builder, obtained from z2h_list_my_listings.
`externalDependencies`	No	Third-party services a Buyer must provision. Common values: Supabase, PostgreSQL, MySQL, MongoDB, Redis, Upstash, Firebase, PlanetScale, Neon, Clerk, Auth0, Stripe, PayPal, Plaid, Resend, SendGrid, Postmark, Twilio, OpenAI, Anthropic.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Listing ID for related-listing references.
`slug`	Yes	Listing identifier used by the other Builder tools.
`status`	Yes	Listing publication state. Only drafts can be edited through MCP.
`editUrl`	Yes	Web wizard URL for editing this listing.
`createdAt`	No	ISO creation timestamp, returned when creating a draft.
`publishUrl`	Yes	Web review step where the Builder finishes publishing.
`termsAcceptance`	No	Present when the Builder needs to accept terms before publishing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 16, 2026

changedInput schema / properties / domains / description

Previous value: -"Industry domain keys from Zero to Hundred taxonomy, such as finance."New value: +"Industry tags for the software. Choose keys from the Zero to Hundred taxonomy: ai, analytics, art-design, auth-identity, cms, conference, developer-tools, devops, e-commerce-marketplace, education, entertainment, environmental, fashion, finance, food, gaming, graphic-design, health, interior-design, marketing, membership, messaging, non-profit, political, productivity, real-estate, religious, services, social, technology, travel, ux-ui, wedding, other. Omission creates a draft without industry tags."

changedInput schema / properties / externalDependencies / items / anyOf

Previous value: -[
-  {
-    "description": "Service name, such as Stripe.",
-    "maxLength": 80,
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "properties": {
-      "cost": {
-        "description": "Expected service cost, such as USD 20/month.",
-        "maxLength": 40,
-        "type": "string"
-      },
-      "name": {
-        "description": "Service the Buyer must provision.",
-        "maxLength": 80,
-        "minLength": 1,
-        "type": "string"
-      },
-      "note": {
-        "description": "What the software needs this service for.",
-        "maxLength": 200,
-        "type": "string"
-      }
-    },
-    "required": [
-      "name"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "description": "Service name, such as Stripe.",
+    "maxLength": 80,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "properties": {
+      "cost": {
+        "description": "Expected service cost, such as USD 20/month.",
+        "maxLength": 40,
+        "type": "string"
+      },
+      "name": {
+        "description": "Name of a service the Buyer needs to operate the software, such as Stripe.",
+        "maxLength": 80,
+        "minLength": 1,
+        "type": "string"
+      },
+      "note": {
+        "description": "What the software needs this service for.",
+        "maxLength": 200,
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  }
+]

changedInput schema / properties / faqs / items / properties / question / description

Previous value: -"Question a Buyer may ask."New value: +"Buyer question addressed by the paired answer."

changedInput schema / properties / shortDescription / description

Previous value: -"One-sentence summary for marketplace cards."New value: +"Buyer-facing summary shown on marketplace cards."

changedInput schema / properties / sourceCodeIncluded / description

Previous value: -"Whether the sale includes source code, as confirmed by the Builder."New value: +"Whether the sale includes source code. Omission records false. Set true only after the Builder confirms that source code is included."

changedInput schema / properties / title / description

Previous value: -"Software name shown to Buyers."New value: +"Name Buyers will see on the software listing."

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description builds on that by explaining the consequence of non-idempotency (check listings before retrying) and stating the required listings:write scope. The defaults for omitted values are also disclosed. It does not explain what the destructive aspect actually affects, so it is strong but not exhaustive.

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: the create action, the returned URLs, and the safety rules all come early. There is mild redundancy between 'return editUrl and publishUrl' and 'Returns the draft identity and web edit/review links', which keeps it from a 5.

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 19-parameter mutation tool with an output schema and rich annotations, the description covers the gaps an agent needs: auth scope, non-idempotency handling, defaulting behavior, and where the workflow continues. Nothing required to invoke it correctly is missing.

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% across 19 parameters, so the schema already documents every field, including defaults, enums and constraints. The description only restates a couple of these (sourceCodeIncluded default, price/source being Builder decisions) without adding format or interaction detail beyond the schema, matching the baseline 3.

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?

Starts with a specific verb+resource ('Create an invisible draft') and immediately states what the call yields (editUrl and publishUrl). It is clearly distinguishable from the sibling update_draft_listing because it establishes that this creates a new, invisible draft rather than mutating an existing one.

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 a real precondition ('Set sourceCodeIncluded only after confirmation'), a retry rule ('Check z2h_list_my_listings before retrying'), and an explicit handoff boundary ('Source delivery, review and publishing continue in the web wizard'). It stops short of routing the agent to z2h_update_draft_listing when the draft already exists, which is the obvious alternative sibling.

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

All Zero to Hundred marketplace tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?