Zero to Hundred marketplace

Update my Zero to Hundred draft

z2h_update_draft_listing

Destructive

Update an owned draft. Omitted fields stay unchanged; nullable fields accept null to clear them. Live listings cannot be edited through this tool. Requires listings:write. Returns the draft identity and web edit/review links. On conflict, read the listing again before retrying.

Input Schema

TableJSON Schema

Name	Required	Description
`faqs`	No	Supplying FAQs disables the automatic FAQ draft.
`mode`	No	Non-exclusive license listing mode. Omit to keep it unchanged.
`slug`	Yes	Listing slug returned by z2h_list_my_listings or z2h_create_draft_listing.
`type`	No	Software category that best matches its main use.
`title`	No	Replacement name Buyers will see on the software listing. Omission keeps the current name.
`demoUrl`	No	Public HTTP or HTTPS demo URL. Null clears it; omission keeps it.
`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 keeps the current 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	Builder-confirmed USD license price. Null clears it; omission keeps it.
`thumbnailUrl`	No	HTTP or HTTPS thumbnail URL. Null clears it; omission keeps it.
`sourceRepoUrl`	No	GitHub repository URL. Null clears it; omission keeps it.
`videoUploadUrl`	No	YouTube or Loom demo URL. Null clears it; omission keeps it.
`longDescription`	No	What the software does, who it helps, and what the Buyer receives.
`operatingStatus`	No	Software readiness or commercial operating state, independent of listing publication. Omission keeps the current state.
`maintenanceLevel`	No	Maintenance commitment the Builder offers.
`shortDescription`	No	Replacement summary for marketplace cards. Omission keeps the current summary.
`documentationLevel`	No	Documentation supplied with the software.
`sourceCodeIncluded`	No	Whether the sale includes source code, as confirmed by the Builder. Omission keeps the current choice.
`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.

Changed7 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 keeps the current 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 / operatingStatus / description

Previous value: -"State of the software itself, independent of the listing publication status."New value: +"Software readiness or commercial operating state, independent of listing publication. Omission keeps the current state."

changedInput schema / properties / shortDescription / description

Previous value: -"One-sentence summary for marketplace cards."New value: +"Replacement summary for marketplace cards. Omission keeps the current summary."

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, as confirmed by the Builder. Omission keeps the current choice."

changedInput schema / properties / title / description

Previous value: -"Software name shown to Buyers."New value: +"Replacement name Buyers will see on the software listing. Omission keeps the current name."

First observedOct 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare the generic safety profile (destructiveHint=true, idempotentHint=false, openWorldHint=true); the description adds real operational context beyond them: PATCH semantics for omitted fields, null-to-clear behavior for nullable fields, the live-listing restriction, the required scope, and conflict recovery. That is substantially more than the structured fields convey.

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?

Five short sentences, front-loaded with the action, then mutation semantics, constraints, prerequisites, and error handling in priority order. No sentence is filler or redundant with the schema.

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 21-parameter mutation tool this covers the essentials: identity requirement, partial-update semantics, exclusion of live listings, authorization scope, and conflict handling. An output schema exists, so the return-value sentence is a bonus rather than a gap-filler.

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 already 100%, so the 21 individual parameters are well documented. The description still contributes cross-cutting parameter semantics that the schema does not state anywhere: omission preserves current values and null explicitly clears them, which is exactly the distinction an agent must get right on a partial update.

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 ('Update an owned draft') and immediately scopes it against siblings: drafts, not live listings, not creation. An agent can distinguish this from z2h_create_draft_listing and z2h_get_listing 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 Guidelines4/5

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

Provides clear when-not guidance ('Live listings cannot be edited through this tool') plus an explicit auth prerequisite (listings:write) and a retry protocol on conflict. It stops short of naming the alternative tool an agent should use for live listings, which is the only remaining routing gap.

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?