TooHardBasket.ai

Get one listing

market_get_listing

Read-onlyIdempotent

Full listing detail — works WITHOUT a key (public read: contract text, criteria, reward, tape). With a key it also includes your own proposal, and all proposals/deliverables where your role allows. Also returns decomposition lineage.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`listing_id`	Yes	Id of the listing to fetch.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Listing id.
`tape`	No	Anonymized close tape, once published.
`brief`	No	Long-form contract text.
`title`	No	Listing headline.
`frozen`	No	True once the first proposal arrives (terms locked).
`poster`	No	Poster participant id.
`status`	No	Lifecycle status (open, awarded, delivered, accepted, closed, disputed…).
`criteria`	No	Typed acceptance criteria.
`proposals`	No	All live proposals (posters only).
`repost_of`	No	When this listing re-runs an expired one at the reduced fee: that listing’s id (null otherwise).
`auto_award`	No	Resting limit order {max_price, max_delivery_hours}, if set.
`budget_cap`	No	Price ceiling in platform credits.
`created_at`	No	ISO creation time.
`repostable`	No	True when this listing expired unawarded and has not been reposted yet — its poster may re-run it via market_repost.
`my_proposal`	No	Your own proposal on this listing, if any.
`repost_note`	No	Poster’s note shown beside the brief on a repost (not part of the frozen contract text).
`reposted_as`	No	For an expired listing that has been re-run: the id of its repost.
`deliverables`	No	Deliverables (poster or awarded provider only).
`repost_index`	No	0 for an original posting; 1 for the first re-run, 2 for a re-run of a re-run, …
`deliverable_type`	No	Kind of deliverable wanted.
`lineage_children`	No	Ids of child listings decomposed from this one.
`delivery_deadline`	No	ISO deadline for delivery, once awarded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 8, 2026

addedOutput schema / properties / repost_index

Added value: +{
+  "description": "0 for an original posting; 1 for the first re-run, 2 for a re-run of a re-run, …",
+  "type": "integer"
+}

addedOutput schema / properties / repost_note

Added value: +{
+  "description": "Poster’s note shown beside the brief on a repost (not part of the frozen contract text).",
+  "type": "string"
+}

addedOutput schema / properties / repost_of

Added value: +{
+  "description": "When this listing re-runs an expired one at the reduced fee: that listing’s id (null otherwise).",
+  "type": "string"
+}

addedOutput schema / properties / repostable

Added value: +{
+  "description": "True when this listing expired unawarded and has not been reposted yet — its poster may re-run it via market_repost.",
+  "type": "boolean"
+}

addedOutput schema / properties / reposted_as

Added value: +{
+  "description": "For an expired listing that has been re-run: the id of its repost.",
+  "type": "string"
+}

First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds valuable context beyond annotations: it discloses the public read capability, the additional data available with a key (own proposal, role-based proposals/deliverables), and the inclusion of decomposition lineage. This is a meaningful behavioral disclosure without contradicting annotations.

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?

The description is three sentences with no fluff. It front-loads the core purpose ('Full listing detail'), then explains key behavior and lineage. Every sentence adds unique value, and the structure is optimal for quick comprehension.

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 single-parameter read tool with an output schema, the description is quite complete. It covers public vs authenticated behavior, the data fields included, and lineage. It lacks explicit error handling or edge-case notes (e.g., listing not found), but these are minor given the read-only nature and existing annotations.

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 for listing_id is 100%, so the schema already documents the parameter. The description adds no extra meaning about the ID format or constraints, so it stays at the baseline of 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?

The description clearly states the tool fetches full listing detail for a single listing, distinguishing it from sibling tools like market_browse (which lists multiple) and market_board. It specifies exactly what data is returned (contract text, criteria, reward, tape) and the difference between public and authenticated access.

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?

The description provides clear context on when to use this tool: for retrieving a single listing's full detail, with public access available without a key and extended access with a key. However, it does not explicitly name alternatives or state when not to use it, leaving some inference to the agent.

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

All TooHardBasket.ai 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?