Skip to main content
Glama

find_videos

Read-only

SEARCH the signed-in user's own YouTube catalogue and LIST the videos that match, by what is written in their titles, descriptions and tags. This is RETRIEVAL, not ranking: call it whenever the user wants to FIND or LIST videos rather than judge them. Use it for 'which of my videos are about X', 'show me every video where I talked about X', 'find my videos mentioning X', 'which videos have a referral or affiliate link in the description', 'list all my videos', 'what have I made about X', or any question whose answer is a SET of their videos. Also use it to pull ONE video's full record (its complete description, tags, length, views): pass that video's title as video. Leave everything empty to browse the whole library newest first. Results are paginated: each answer says how many matched and the offset to pass to see the next page, so keep asking to walk a large catalogue rather than stopping at the first page. It searches only what the creator WROTE, never what is spoken in the video. For how a video PERFORMED use analyze_video; for the best performers use find_best_videos. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoOnly videos published on or after this ISO date
limitNoMatches per page (default 50, max 200)
queryNoWords that must all appear in the title, description or tags
titleNo
videoNoOne video's title, to get its full record instead of a list
beforeNoOnly videos published on or before this ISO date
formatNoOnly Shorts, or only long-form
offsetNoSkip this many matches; use the offset the previous answer gave

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds materially beyond that: pagination semantics (each answer returns a match count and the offset to continue, so the agent should walk pages), the fact that it reads the signed-in user's connected channel directly with no auth or clarifying questions needed, and the scope limit that transcripts are never searched. It also discloses the empty-input default ordering (whole library, newest first).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The routing information is front-loaded and the alternatives come last, which is good structure, but the body is padded: seven quoted example queries, heavy ALL-CAPS emphasis, and a closing 'never ask the creator anything' sentence that restates the earlier no-input claim. Roughly a third of the text is repetition that could be trimmed without losing routing value.

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 an eight-parameter, zero-required retrieval tool with no output schema, the description covers the essentials an agent needs: what gets matched, how results are paged, how to fetch a single record, what the no-argument behavior is, and where to go for performance instead. Nothing needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 88%, so the baseline is 3; the description pushes higher by explaining that an empty call browses the whole library newest first, that `video` takes a title to return one full record instead of a list, and that `offset` should come from the previous answer's reported offset. It does not disambiguate the near-duplicate `video` vs `title` parameters or explain how `query` matching combines with `after`/`before`/`format`.

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 ('SEARCH ... catalogue and LIST the videos') plus the exact match surface (titles, descriptions, tags) and explicitly frames itself as RETRIEVAL not ranking. It names the siblings it is not (analyze_video for performance, find_best_videos for top performers), so an agent can route 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 Guidelines5/5

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

Gives both when-to-use (five quoted user phrasings covering search, listing, link-in-description, and single-video lookup) and when-not-to-use with the two named alternatives. It also adds a negative condition ('searches only what the creator WROTE, never what is spoken'), which is exactly the kind of exclusion that prevents wrong routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources