Zero to Hundred marketplace

Get my Zero to Hundred listing

z2h_get_listing

Read-onlyIdempotent

Read one owned listing before editing it. Requires listings:read. Use a slug from z2h_list_my_listings. Returns descriptions, pricing, software attributes, source attachment state and web edit links. Missing listings and listings owned by someone else both return not found. This does not download source code.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Identifies one of the authenticated Builder's listings. Copy slug from z2h_list_my_listings or z2h_create_draft_listing.

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.
`type`	Yes	Software category.
`title`	Yes	Software name.
`status`	Yes	Listing publication state. Only drafts can be edited through MCP.
`demoUrl`	Yes	Public demo URL, or null.
`domains`	Yes	Industry domain taxonomy keys.
`editUrl`	Yes	Web wizard URL for editing this listing.
`createdAt`	Yes	ISO creation timestamp.
`imageUrls`	Yes	Listing screenshot URLs.
`techStack`	Yes	Frameworks and languages used.
`updatedAt`	Yes	ISO last-update timestamp.
`createdVia`	Yes	Recorded creation channel.
`publishUrl`	Yes	Web review step where the Builder finishes publishing.
`sourceKind`	Yes	Source attachment method, or null before attachment.
`testEnvUrl`	Yes	Legacy stored demo URL, or null.
`askingPrice`	Yes	USD license price, or null when unset.
`thumbnailUrl`	Yes	Marketplace thumbnail URL, or null.
`sourceRepoUrl`	Yes	Source repository URL, or null.
`longDescription`	Yes	Full software description.
`operatingStatus`	Yes	Operating state of the software, independent of listing publication.
`maintenanceLevel`	Yes	Builder maintenance commitment, or null when unset.
`shortDescription`	Yes	Marketplace card summary.
`documentationLevel`	Yes	Documentation supplied, or null when unset.
`sourceCodeIncluded`	Yes	Whether the Builder included source code.
`testEnvInstructions`	Yes	Legacy stored demo instructions, or null.
`externalDependencies`	Yes	Services the Buyer must provision. Legacy records may contain service names as strings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / slug / description

Previous value: -"Owned listing slug from z2h_list_my_listings or z2h_create_draft_listing."New value: +"Identifies one of the authenticated Builder's listings. Copy slug from z2h_list_my_listings or z2h_create_draft_listing."

First observedOct 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld), it discloses the required scope (listings:read), the error semantics (missing and other-owned listings both collapse to not found), the shape of the payload, and an explicit non-goal. That is substantial context the annotations cannot carry.

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, front-loaded sentences with no filler: purpose, prerequisite, slug source, return contents, error behavior, non-goal. Every sentence carries distinct information.

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?

Covers auth requirement, prerequisite call, error semantics, and scope, and the return contents are confirmed by an existing output schema. Nothing an agent needs to select and invoke this tool 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% and the single slug parameter is fully documented there, so baseline is 3. The description's "Use a slug from z2h_list_my_listings" merely restates what the schema already says about the slug's origin.

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 ("Read one owned listing") plus the scope constraint "owned" and the moment of use ("before editing it"). An agent can distinguish it from z2h_list_my_listings (many) and z2h_update_draft_listing (write) 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?

Gives clear context (read before editing) and names the upstream source of the slug (z2h_list_my_listings, echoed in the schema). It also draws one explicit non-goal ("does not download source code"), but never names z2h_update_draft_listing or z2h_confirm_source_upload as the tools to use after/beside it.

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?