ES

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

Desarrollador
Precios
Desde 0,00035 US$ / registro
Última actualización
2026-09-18

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 nameChannel IDChannel URLSubmitted accountNo data
Ulanzi Japan(ウランジ)UCUo0_zutHjxAwHnrTHFph_ghttps://www.youtube.com/@UlanziJapanUlanziJapanNo
DemoChannelYes

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 desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.

  1. 1If no profile data is returned, verify the account or channel name and confirm the channel is still public
  2. 2Retry later after rate limiting, temporary unavailability, or a timeout
  3. 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
  4. 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.

  • YouTube account listitemsObligatorioarray<object>
    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.
    Cantidadhasta 200 elementosEjemplo[{"account":"UlanziJapan","needMoreInfo":true}]

Salida

Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.

  • Submitted accounttask_itemstring
    The account or channel name submitted for this record
    EjemploUlanziJapan
  • No datano_databoolean
    Whether this submitted account returned no public profile
    Ejemplofalse
  • Source keywordkeywordstring
    The source keyword associated with the collected account
    EjemploUlanziJapan
  • Channel IDaccount_idstring
    The YouTube channel identifier returned for the profile
    EjemploUCUo0_zutHjxAwHnrTHFph_g

Datos de ejemplo

Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.

output.example
{
  "task_item": "UlanziJapan",
  "no_data": false,
  "keyword": "UlanziJapan",
  "account_id": "UCUo0_zutHjxAwHnrTHFph_g",
  "account_name": "Ulanzi Japan(ウランジ)",
  "account_home_url": "https://www.youtube.com/@UlanziJapan",
  "biz_id": "UlanziJapan",
  "email": "<email>",
  "fans_count": "<fans_count>",
  "fan_nums_origin": "<fan_nums_origin>",
  "location": "<location>",
  "country": "<country>",
  "joined_date": "<joined_date>",
  "links": "[]",
  "views_num": "<views_num>",
  "publish_content_count": "<publish_content_count>",
  "clean_update_time": "2026-08-27T14:19:57",
  "crawl_time": "2026-08-27T14:19:57"
}

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. Esta App se ejecuta de forma asíncrona y se puede cancelar a mitad de camino: Tras la cancelación, la ejecución se detiene. Los registros ya entregados se conservan y se facturan.

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 config
{
  "mcpServers": {
    "octoparse_datahub": {
      "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. (De forma predeterminada te guía para iniciar sesión y nunca te pide que envíes tu API Key en el chat.)

detail.access.mcp.composeHint

Precios

Task start

Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.

0,0001 US$/ ejecución
Returned profile

Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran.

0,00035 US$/ registro

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éditos

Pruébalo ahora

Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.

Ejemplo
Los parámetros se validan contra input.schema antes del envío
Desde 0,00035 US$ / registro