Skip to main content
Glama
youtube-transcript-leads-mcp

youtube-transcript-leads-mcp

by willowswt

find_youtube_channel_emails

Read-onlyIdempotent

Find YouTube channels by niche keyword or @handle, then extract verified business inquiry emails, sponsor links, and social handles for outreach.

Instructions

Discover YouTube channels by niche keyword or @handle and extract verified business inquiry emails, sponsor links, and social handles.

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_youtube_channel_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum unique channels to discover and enrich.
channelUrlsNoSpecific YouTube channel URLs, @handles, or UC channel IDs.
searchQueriesNoNiche keywords or topics (e.g. ['AI automation agency', 'SaaS marketing']).
onlyWithEmailsNoFilter out channels without any discovered email.
scanRecentVideosNoNumber of recent video descriptions to scan per channel.
crawlExternalLinksNoFollow Linktree/Beacons and contact pages for emails.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds valuable output context (verified emails, sponsor links, social handles) that the annotations cannot convey, but it omits operational traits such as latency, rate limits, or that many channels will yield no email.

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?

A single front-loaded sentence that names the input modes first and the enrichment outputs second, with no filler or redundant restatement of the tool name.

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?

With no output schema, the description usefully enumerates what comes back (emails, sponsor links, social handles), and all six parameters are documented in the schema. The main remaining gap is guidance on cost/expectations for a crawling tool, which prevents a 5.

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%, so every parameter (maxResults, channelUrls, searchQueries, onlyWithEmails, scanRecentVideos, crawlExternalLinks) is already documented. The description's mention of 'niche keyword or @handle' merely restates the two input modes and adds no syntax, default, or interaction detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs specific verbs ('discover', 'extract') with specific resources (YouTube channels, business inquiry emails, sponsor links, social handles), so an agent knows exactly what the tool produces. It does not explicitly contrast itself with the sibling transcript tool, but the discovery/enrichment scope is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the wording suggests prospecting/enrichment work, and the two input modes (keyword vs. @handle) are hinted at. There is no explicit when-to-use, when-not-to-use, or mention of alternatives such as the transcript tool, and no note that this is a multi-step scraping operation that can be slow or return empty results.

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