Servidor MCP para el actor YouTube Channel Stats Extractor de Mamba Labs en Apify.
Resuelve un dominio de empresa o un identificador de YouTube al canal con el número de suscriptores y los metadatos del canal.
Resuelve un dominio de empresa, o un identificador de YouTube, al canal de YouTube de esa empresa. Devuelve el número de suscriptores, el ID de canal UC estable, el nombre del canal, la fecha de creación y la descripción, como una fila plana lista para Clay. YouTube redondea los recuentos de suscriptores por encima de aproximadamente mil suscriptores, tanto en la página como en su API oficial, y la fila lo indica. La extracción opcional de transcripciones está disponible y actualmente está RESTRINGIDA por YouTube: la lista de pistas de subtítulos es legible y el endpoint de contenido de subtítulos devuelve un cuerpo vacío sin un token de prueba de origen, que la fila informa como not_extractable en lugar de que un video no tenga subtítulos. No se necesita clave de API. Solo lectura; requiere un APIFY_TOKEN y consume créditos de Apify por llamada.
Related MCP server: YouTube MCP
Añade esto a la configuración de tu cliente MCP:
{
"mcpServers": {
"mamba-youtube-channel-stats": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-youtube-channel-transcript-extractor"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Node.js 18 o superior
Un token de API de Apify desde console.apify.com/account/integrations
El actor se paga por evento y consume créditos de Apify por llamada. Los precios están en la página del actor.
"¿Cuántos suscriptores de YouTube tiene stripe.com?"
"Encuentra el ID del canal de YouTube para hubspot.com."
"¿Gitlab.com tiene un canal de YouTube y cuándo se creó?"
Herramienta: get_youtube_channel_stats
Entrada | Tipo | Significado |
| string | Dominio de empresa simple, por ejemplo shopify.com. Proporciona esto o un identificador. Con un dominio, el actor realiza un descubrimiento completo; con un identificador, salta directamente a |
| string | Opcional. Mejora la precisión de la búsqueda y es lo que la puerta de identidad comprueba contra un perfil descubierto, por lo que proporcionarlo reduce coincidencias incorrectas. |
| string | Opcional. Un identificador de YouTube como @shopify, o una URL completa del canal. Proporcionarlo omite el descubrimiento y va directamente al canal. |
| boolean | Cuando es "true" (por defecto) se obtiene la página del perfil y se extraen los recuentos. Establece "false" para resolver solo la URL del perfil, que es más barato y necesita |
| boolean | Cuando es "false" (por defecto) una búsqueda exitosa se almacena en caché durante siete días y se reutiliza. Establece "true" para forzar una nueva obtención. Se envía como cadena para compatibilidad con Clay |
| boolean | Cuando es "true", se extraen transcripciones completas con marcas de tiempo para los videos más recientes del canal y se devuelven como una fila por video. El valor predeterminado es "false" porque |
| string | Cuántos de los videos más recientes del canal se deben extraer transcripciones, cuando las transcripciones están activadas. Por defecto 5. Cada video es una obtención adicional y una adicional |
Cada fila lleva un campo _status por plataforma, y es el campo que se debe leer primero. El vocabulario es el mismo en toda la familia social de Mamba Labs:
Estado | Significado |
| obtenido y analizado, el valor está ahí |
| buscamos y no existe tal perfil |
| el perfil existe y el valor no está disponible para nosotros |
| la plataforma nos rechazó, vale la pena reintentar más tarde |
| encontramos un perfil real y pertenece a otra persona |
| no pediste esta plataforma |
false y null nunca son intercambiables. false significa que buscamos y la respuesta es no. null significa que no pudimos buscar. Si filtras por empresas sin presencia, filtra por false, porque las filas null son desconocidas en lugar de ausentes.
apify.com/mambalabs/youtube-channel-transcript-extractor
Mamba Labs construye una flota de actores de enriquecimiento GTM que comparten una convención de salida plana y lista para Clay, por lo que sus filas se unen en company_domain sin paso de limpieza. Flota completa: apify.com/mambalabs
MIT
Resolve a company domain, or a YouTube handle, to that company's YouTube channel. Returns the subscriber count, the stable UC channel id, channel name, creation date and description, as one flat Clay ready row. Subscriber counts are rounded by YouTube above roughly a thousand subscribers, on the page and in its official API alike, and the row flags that. Optional transcript pulling is available and is CURRENTLY GATED by YouTube: the caption track list is readable and the caption content endpoint returns an empty body without a proof of origin token, which the row reports as not_extractable rather than as a video having no captions. A company with no channel reports youtube_status not_found. Read youtube_status before any count. Use it to look up one known company channel per call; it does not search YouTube, list a channel's videos, or return video detail, and the package name mentions transcripts only because transcript pulling is an option. No API key needed. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | No | Optional. A YouTube handle such as @shopify, or a full channel URL. Supplying it skips discovery and goes straight to the channel. | |
| skipCache | No | When "false" (default) a successful lookup is cached for seven days and reused. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility. | |
| company_name | No | Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches. | |
| company_domain | No | Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to the fetch. | |
| max_charge_usd | No | Optional spending cap for this call, in USD, passed to the actor as max_charge_usd. The run stops before any charge that would take it past this amount and keeps every row already charged. Leave empty to rely only on the maximum charge per run set on your Apify account. | |
| includeTranscripts | No | When "true", full timestamped transcripts are pulled for the most recent videos on the channel and returned as one row per video. Default is "false" because transcripts are the expensive half of this actor and most buyers want channel stats only. Sent as a string for Clay compatibility. | |
| transcriptVideoCount | No | How many of the channel's most recent videos to pull transcripts for, when transcripts are on. Default 5. Each video is one extra fetch and one extra billable transcript event, so this is the dial that sets the cost of a transcript run. | |
| includeFollowerCounts | No | When "true" (default) the profile page is fetched and the counts are extracted. Set "false" to resolve the profile URL only, which is cheaper and needs no proxy. Sent as a string for Clay compatibility. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description is otherwise unusually candid — YouTube's subscriber rounding, the transcript gating and the not_extractable vs. no-captions distinction, credit consumption, and the APIFY_TOKEN requirement are all disclosed. However, it asserts 'Read only' while the annotations declare readOnlyHint=false, an outright conflict on the safety profile. Flagged as an annotation contradiction, which caps this score.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose and return shape are front-loaded, and the caveats (rounding, gating, status field, cost) follow in descending priority. It runs long at roughly nine sentences, and the aside about the package name is borderline, but almost every sentence carries information an agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 8 optional parameters and no output schema, the description does the heavy lifting: it names the return fields, the flat-row shape, the youtube_status signal, and the not_found case, plus auth and billing. It stops short of enumerating all possible youtube_status values or how a missing domain+handle is handled, which keeps it from a 5.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantics beyond it: transcripts are CURRENTLY GATED by YouTube and the row reports not_extractable rather than no-captions, which materially changes how an agent should interpret includeTranscripts/transcriptVideoCount results. It also explains the cost framing of a transcript run rather than leaving it to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a precise verb+resource: resolve a domain or handle to a company's YouTube channel, then lists the returned fields (subscriber count, UC id, name, creation date, description). It also explicitly fences the scope — 'it does not search YouTube, list a channel's videos, or return video detail' — so an agent knows exactly what this tool is and is not.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives direct usage guidance: 'Use it to look up one known company channel per call', with explicit exclusions (no search, no video listing, no video detail) and a sequencing rule ('Read youtube_status before any count'). The domain-vs-handle choice and its consequence (full discovery vs. straight to fetch) is stated inline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.1.1get_youtube_channel_stats2 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / properties / max_charge_usdAdded value: +{
+ "description": "Optional spending cap for this call, in USD, passed to the actor as max_charge_usd. The run stops before any charge that would take it past this amount and keeps every row already charged. Leave empty to rely only on the maximum charge per run set on your Apify account.",
+ "minimum": 0,
+ "type": "number"
+}v1.0.0get_youtube_channel_statsScored across 1 tool
With only one tool there is nothing to confuse it with, and the description clearly enumerates what it does (domain/handle → channel stats) and what it does not do (search, video listing, video detail). The only mild internal blur is that the tool name advertises transcripts while the body frames them as a gated option, but that is a scoping note, not a tool-selection ambiguity.
The single tool follows a clean snake_case verb_noun pattern (get_youtube_channel_stats). No mixing of conventions or vague verb styles is present to break predictability.
One tool is thin for a server that also implies transcript extraction and channel resolution; resolving, stats, and transcript pulling are collapsed into a single overloaded call. It is not mis-scoped enough to be wrong, but it sits at the borderline of too few.
Channel lookup and stats are covered, but the headline transcript capability is effectively unusable (caption content gated, reported as not_extractable), and there is no video listing, video detail, or multi-channel/batch operation. An agent can still retrieve channel stats, so gaps are notable rather than fatal.
YouTube video metadata, transcripts and channel data by URL or @handle. No API key. Pay per result.
Find the contact email of YouTube channels from the link, the @handle or the channel_id. Resolves th
YouTube search, whole channels, video stats, comments and full transcripts with timestamps.
YouTube data for AI agents: channels, videos, transcripts, comments, search. Video research.