bidclub

List episodes

bidclub_list_episodes

List episodes newest first, optionally narrowed to one show. Returns metadata only — titles, deks, dates, durations, participant chips and source links — never the digest or transcript. Use bidclub_get_episode for content.

Input Schema

TableJSON Schema

Name	Required	Description
`show`	No	Show id from bidclub_list_shows. Omit for the whole library.
`asset`	No	Optional asset tag ids joined by commas (equities, crypto, vc_pe, other). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.
`focus`	No	Optional focus tag ids joined by commas (investing, company_building, technical, macro, policy). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.
`limit`	No	Episodes per page.
`offset`	No	Rows to skip. Page with the returned pagination.next_offset.
`sector`	No	Optional sector tag ids joined by commas (ai_software, semis, robotics, biotech, consumer, finance, blockchain, energy, space_defense). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.
`source_lang`	No	Filters by the episode's ORIGINAL language. Chinese digests exist for most English-source episodes, so do NOT set source_lang=ZH just because you want Chinese output — use the lang parameter on bidclub_get_episode instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 18, 2026

addedInput schema / properties / asset

Added value: +{
+  "description": "Optional asset tag ids joined by commas (equities, crypto, vc_pe, other). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.",
+  "pattern": "^(?:none|(?:equities|crypto|vc_pe|other)(?:,(?:equities|crypto|vc_pe|other))*)$",
+  "type": "string"
+}

addedInput schema / properties / focus

Added value: +{
+  "description": "Optional focus tag ids joined by commas (investing, company_building, technical, macro, policy). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.",
+  "pattern": "^(?:none|(?:investing|company_building|technical|macro|policy)(?:,(?:investing|company_building|technical|macro|policy))*)$",
+  "type": "string"
+}

addedInput schema / properties / sector

Added value: +{
+  "description": "Optional sector tag ids joined by commas (ai_software, semis, robotics, biotech, consumer, finance, blockchain, energy, space_defense). Matches any selected id within this facet and all supplied facets together. Omit for all episodes, including untagged; pass none for no episodes.",
+  "pattern": "^(?:none|(?:ai_software|semis|robotics|biotech|consumer|finance|blockchain|energy|space_defense)(?:,(?:ai_software|semis|robotics|biotech|consumer|finance|blockchain|energy|space_defense))*)$",
+  "type": "string"
+}

First observedAug 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns metadata only (titles, deks, dates, durations, participant chips, source links) and never the digest or transcript, which is a key behavioral trait. It also states ordering (newest first). However, it does not mention pagination details or other side effects, though such details exist in the schema. This disclosure is substantial 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a two-sentence composition: the first sentence front-loads the purpose and optional filter, the second specifies output scope and routes to the alternative. Every word serves a purpose, with no repetition or fluff, making it highly concise and structurally effective.

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?

Given the 7 parameters fully described in the schema and the absence of an output schema, the description adequately covers what is returned (metadata fields) and what is not (content). It does not explicitly mention pagination via next_offset, but that is documented in the offset parameter. The facet filtering (asset, focus, sector) is not described in the description, but the schema covers it. Overall, the description is nearly complete for effective tool invocation, with minor gaps that the schema fills.

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% for all 7 parameters. The description adds minimal parameter-specific meaning beyond the schema; it only reinforces the 'show' filter with 'optionally narrowed to one show,' which is already present in the parameter description. Per the baseline rule for high schema coverage, a score of 3 is appropriate.

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 lists episodes newest first, with an optional filter for a single show. It explicitly defines the resource (episodes), the ordering (newest first), and contrasts with bidclub_get_episode for content, making the purpose distinctive and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly says 'Use bidclub_get_episode for content,' directly routing the agent when content (digest/transcript) is needed. It also notes 'optionally narrowed to one show,' giving a clear filter context. This is explicit guidance on when to use this tool versus an alternative.

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

All bidclub 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?