docs: channel/videos sort + members_only across the plugin's API surface - #12
Merged
Merged
Conversation
All four places this repo enumerates the endpoint now carry it: README tool 8, the SKILL.md routing table plus credit-hygiene notes, references/mcp-tools.md and references/rest-api.md. Each leads with the same framing: existing calls are untouched, and sort=latest is a different view (the Videos tab, Shorts excluded) rather than a re-ordering of the uploads feed. Verified empirically on three channels: 0 of the Shorts a channel publishes appear in any sorted feed, while 43/48 (@ted), 12/40 (@nasa) and 30/48 (@natgeo) appear in the unsorted uploads feed. Per-tab field presence recorded honestly: tab=streams carries lengthText and publishedTimeText, tab=shorts returns null for both, and the channel-tab feeds null out channelId/channelTitle/channelHandle/index. Docs only, no version bump. Co-Authored-By: CRHQ <noreply@crhq.ai>
therohitdas
force-pushed
the
docs/channel-videos-sort
branch
from
September 21, 2026 10:58
1c3a696 to
b2a1471
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the live
sort=latest|popular|oldestparam and the additivemembers_onlyfield wherever this plugin enumerates thechannel/videossurface.Do not merge or publish yet — this is for the Lead's gate.
Files
This repo describes the same endpoint in four places, and all four drifted without this:
README.md— tool 8,list_channel_videos:sortrow + the opt-in table +members_only+ per-tab fields.skills/youtube/SKILL.md— a new routing-table row for the sorted case, and a credit-hygiene bullet telling the agent when not to reach forsort.skills/youtube/references/mcp-tools.md— the MCP-shaped parameter table.skills/youtube/references/rest-api.md— the REST-shaped parameter table, the request examples, and the validation-rules table.The point every file leads with
Omitting
sortis not the same assort=latest:tab=videos, nosorttab=videos+ anysortplaylist_infonulltab=shorts)members_only: trueDifferent sets, not one list in two orders — and a sorted crawl costs ~3.3x the pages and credits. The
SKILL.mdbullet is written as a don't for exactly that reason: an agent reading the routing table will otherwise setsortby reflex and triple the user's bill.Per-tab fields (verified live on @ted / @nasa / @natgeo)
tab=streamscarrieslengthTextandpublishedTimeText(Streamed 2 years ago;LIVEplus a watching count while live).tab=shortsreturnsnullfor both — YouTube's Shorts grid publishes neither.channelId/channelTitle/channelHandle/indexarenull.Verification
Both the REST shape and the MCP shape were checked against prod, not inferred:
GET /api/v2/youtube/channel/videosacross{no sort, latest, popular, oldest} x {videos, shorts, streams}, andtools/listonhttps://transcriptapi.com/mcp, which returnslist_channel_videoswithsorttypedenum: [latest, popular, oldest] | null, defaultnull.Needs
Version bump: not applied. Docs-only, but
skills/youtube/ships inside the published plugin, so if the Lead republishes to the marketplace/registry off the back of this, the manifest versions want a patch bump first. Flagging rather than guessing the scheme.Marketing pass: the "~3.3x the credits" line now appears in all four files. Accurate, and deliberately discouraging — the Lead may want softer phrasing in the public
README.mdwhile keeping the blunt version in the agent-facingSKILL.md, where the discouragement is the whole point.