Zero to Hundred marketplace

List my Zero to Hundred listings

z2h_list_my_listings

Read-onlyIdempotent

Find the authenticated Builder's drafts and live listings before creating another draft. Requires listings:read. Returns items with slugs, publication state, USD prices, edit links, and nextCursor. Pass nextCursor to continue paging; null ends the list. An invalid or expired token requires sign-in again.

Input Schema

Name	Required	Description
`limit`	No	Number of owned listings to return per page. Omission uses 25, with newest listings first.
`cursor`	No	Continue after the last listing in the preceding result. Use that response's nextCursor; omission starts at the newest listing.
`setupCode`	No	Temporary code from the Zero to Hundred connection check. Omit for ordinary listing reads.

Output Schema

Name	Required	Description	Default
`items`	Yes	The authenticated Builder's listings, newest first.
`nextCursor`	Yes	Opaque cursor for the next page, or null at the end.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 27, 2026
- removedOutput schema / properties / items / items / properties / askingPrice / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / askingPrice / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / demoUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / demoUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / thumbnailUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / thumbnailUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / nextCursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / nextCursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedOct 18, 2026

addedInput schema / properties / setupCode

Added value: +{
+  "description": "Temporary code from the Zero to Hundred connection check. Omit for ordinary listing reads.",
+  "pattern": "^[a-f0-9]{32}$",
+  "type": "string"
+}

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / cursor / description

Previous value: -"Opaque nextCursor from the previous page. Omit for the first page."New value: +"Continue after the last listing in the preceding result. Use that response's nextCursor; omission starts at the newest listing."

changedInput schema / properties / limit / description

Previous value: -"Listings per page. Defaults to 25; newest first."New value: +"Number of owned listings to return per page. Omission uses 25, with newest listings first."

First observedOct 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: states the required scope (listings:read), enumerates what is returned (slugs, publication state, USD prices, edit links, nextCursor), explains paging termination (null ends the list), and describes the expired-token recovery path. This is the behavioral context an agent needs before calling.

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, front-loaded with purpose and scoping, then prerequisites, returns, and paging. No filler and nothing repeated from structured fields unnecessarily.

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 read-only paginated list tool with an output schema, this covers everything: auth scope, page size default behavior, continuation semantics, and failure handling. Nothing an agent needs 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 coverage is 100%, so limit and cursor are already documented in the schema; the description only reinforces cursor-based continuation. It says nothing about the setupCode connection-check parameter, which is left entirely to 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 ('Find the authenticated Builder's drafts and live listings') with clear ownership scope, which separates it from z2h_get_listing and z2h_search_marketplace. The mention of checking before creating another draft fixes the intent precisely.

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 clear trigger: use it before creating another draft, implicitly routing the agent away from z2h_create_draft_listing when a duplicate may exist. It does not explicitly name exclusions or alternatives for the search/compare siblings, but the context is unambiguous.

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.