YouTube Account Info
Collect public channel profiles, audience metrics, and contact signals for one or more YouTube accounts
Original · en-USVolver a la traducción
Descripción general
YouTube channel pages mix branding, audience size, and contact details in a layout that is hard to compare across accounts. This app turns those public channel profiles into a consistent record set so research, partnership, and monitoring teams can work from the same identifiers, metrics, and timestamps.
The value is the joined profile snapshot: channel identity, displayed name, public URL, follower and view figures, location, join date, and publicly shown contact details stay together for each submitted account. That makes it easier to qualify channels, compare audience scale, and keep a watch list current without reconstructing profiles by hand.
Data notes
The data comes from the public YouTube channel profile associated with each submitted account or channel name. One record is produced for each submitted account when the source returns a profile or a no-data marker. Duplicate submitted accounts are removed across collected pages. Audience counts, location, country, join date, links, and timestamps retain the source text; a source value can be unavailable and appear empty. Timestamps are preserved as supplied, without inferring a timezone. Private, terminated, and login-only channels are outside the coverage.
What the results look like
Each record represents the public profile collected for one submitted YouTube account.
| Channel name | Channel ID | Channel URL | Submitted account | No data |
|---|---|---|---|---|
| Ulanzi Japan(ウランジ) | UCUo0_zutHjxAwHnrTHFph_g | https://www.youtube.com/@UlanziJapan | UlanziJapan | No |
| DemoChannel | Yes |
Additional values include Source keyword, Business ID, Public email, Follower count, Raw follower text, Location, Country, Joined date, Profile links, View count, Video count, Source updated at, and Collected at.
Use cases
- Qualify partnership targets by comparing Channel name, Channel ID, and Follower count across a watch list.
- Map public presence by lining up Channel URL, Location, Country, and Joined date for channels you already monitor.
- Separate empty outcomes from usable profiles by checking No data together with Submitted account before using View count or Video count.
- Keep a collection log by comparing Source updated at with Collected at when the same Submitted account is reviewed again.
Alcance y límites
Each run accepts 1 to 200 YouTube accounts or channel names and returns public profile records when data is available.
- Adecuada para
- When you need a current public profile snapshot for specific YouTube channels
- When you need displayed audience size, location, join date, and public contact details in one record
- No usar para
- When you need video lists, comments, or search results rather than channel-level profile information
- When you do not have a YouTube account or channel name to collect
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el autor. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 1If no profile data is returned, verify the account or channel name and confirm the channel is still public
- 2Retry later after rate limiting, temporary unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4If authentication fails, verify the API Key configured for the execution environment
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
| Campo | Nombre de negocio | Tipo | Obligatorio | Predeterminado | Enum / Restricciones | Ejemplo | Descripción |
|---|---|---|---|---|---|---|---|
| items | YouTube account list | array<object> | Sí | — | hasta 200 elementos | [{"account":"UlanziJapan","needMoreInfo":true}] | The YouTube accounts or channel names to collect. Submit 1 to 200 items; each item needs an account value and whether to collect extra details. |
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
| Campo | Nombre de negocio | Tipo | Ejemplo | Descripción |
|---|---|---|---|---|
| task_item | Submitted account | string | UlanziJapan | The account or channel name submitted for this record |
| no_data | No data | boolean | false | Whether this submitted account returned no public profile |
| keyword | Source keyword | string | UlanziJapan | The source keyword associated with the collected account |
| account_id | Channel ID | string | UCUo0_zutHjxAwHnrTHFph_g | The YouTube channel identifier returned for the profile |
| account_name | Channel name | string | Ulanzi Japan(ウランジ) | The displayed YouTube channel name |
| account_home_url | Channel URL | string | https://www.youtube.com/@UlanziJapan | The public YouTube channel URL |
| biz_id | Business ID | string | UlanziJapan | The business identifier carried by the source profile record |
| Public email | string | — | The contact email shown on the public channel profile when available | |
| fans_count | Follower count | string | — | The displayed follower count retained as source text |
| fan_nums_origin | Raw follower text | string | — | The original follower-count text supplied by the source |
| location | Location | string | — | The location text displayed on the channel profile |
| country | Country | string | — | The country text displayed on the channel profile |
| joined_date | Joined date | string | — | The channel joined date as displayed by the source |
| links | Profile links | string | [] | Public profile links retained as source text |
| views_num | View count | string | — | The displayed total view count retained as source text |
| publish_content_count | Video count | string | — | The displayed public video or content count retained as source text |
| clean_update_time | Source updated at | string | 2026-08-27T14:19:57 | The source timestamp when the profile data was updated |
| crawl_time | Collected at | string | 2026-08-27T14:19:57 | The source timestamp when the channel profile was collected |
Schema del registro
La salida se devuelve registro a registro. detail.output.idFieldHint
{
"type": "object",
"properties": {
"task_item": {
"type": "string",
"title": "Submitted account",
"description": "The account or channel name submitted for this record",
"prefill": "UlanziJapan"
},
"no_data": {
"type": "boolean",
"title": "No data",
"description": "Whether this submitted account returned no public profile",
"prefill": false
},
"keyword": {
"type": "string",
"title": "Source keyword",
"description": "The source keyword associated with the collected account",
"prefill": "UlanziJapan"
},
"account_id": {
"type": "string",
"title": "Channel ID",
"description": "The YouTube channel identifier returned for the profile",
"prefill": "UCUo0_zutHjxAwHnrTHFph_g"
},
"account_name": {
"type": "string",
"title": "Channel name",
"description": "The displayed YouTube channel name",
"prefill": "Ulanzi Japan(ウランジ)"
},
"account_home_url": {
"type": "string",
"title": "Channel URL",
"description": "The public YouTube channel URL",
"prefill": "https://www.youtube.com/@UlanziJapan"
},
"biz_id": {
"type": "string",
"title": "Business ID",
"description": "The business identifier carried by the source profile record",
"prefill": "UlanziJapan"
},
"email": {
"type": "string",
"title": "Public email",
"description": "The contact email shown on the public channel profile when available"
},
"fans_count": {
"type": "string",
"title": "Follower count",
"description": "The displayed follower count retained as source text"
},
"fan_nums_origin": {
"type": "string",
"title": "Raw follower text",
"description": "The original follower-count text supplied by the source"
},
"location": {
"type": "string",
"title": "Location",
"description": "The location text displayed on the channel profile"
},
"country": {
"type": "string",
"title": "Country",
"description": "The country text displayed on the channel profile"
},
"joined_date": {
"type": "string",
"title": "Joined date",
"description": "The channel joined date as displayed by the source"
},
"links": {
"type": "string",
"title": "Profile links",
"description": "Public profile links retained as source text",
"prefill": "[]"
},
"views_num": {
"type": "string",
"title": "View count",
"description": "The displayed total view count retained as source text"
},
"publish_content_count": {
"type": "string",
"title": "Video count",
"description": "The displayed public video or content count retained as source text"
},
"clean_update_time": {
"type": "string",
"title": "Source updated at",
"description": "The source timestamp when the profile data was updated",
"prefill": "2026-08-27T14:19:57"
},
"crawl_time": {
"type": "string",
"title": "Collected at",
"description": "The source timestamp when the channel profile was collected",
"prefill": "2026-08-27T14:19:57"
}
},
"required": [],
"additionalProperties": false
}Integración
Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino.
Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.
Configuración del cliente
Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.
{
"mcpServers": {
"hello_moto__youtube-account-info": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/youtube-account-info",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Deja que la IA lo configure por ti
¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (El prompt le pide a la IA que te solicite tu API Key, de modo que las credenciales nunca queden en el historial de chat ni en configuraciones compartidas.)
detail.access.mcp.composeHint
Precios
Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.
Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran.
Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.
Ver créditosPruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.