YouTube Account Info
Collect public channel profiles, audience metrics, and contact signals for one or more YouTube accounts
Original · en-USZur Übersetzung
Übersicht
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.
Anwendungsbereich & Grenzen
Each run accepts 1 to 200 YouTube accounts or channel names and returns public profile records when data is available.
- Geeignet für
- 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
- Nicht verwenden für
- 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
Fehlerbehandlung
Vom Autor deklariertes Fehler- und Wiederholungsverhalten. Wir empfehlen, es bei der Integration in Ihren System-Prompt aufzunehmen.
- 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
Eingabe
Parameter, die zum Aufruf dieser App erforderlich sind, generiert aus dem input.schema in der manifest.json.
| Feld | Fachlicher Name | Typ | Erforderlich | Standard | Enum / Einschränkungen | Beispiel | Beschreibung |
|---|---|---|---|---|---|---|---|
| items | YouTube account list | array<object> | Ja | — | bis zu 200 Einträge | [{"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. |
Ausgabe
Feldstruktur eines einzelnen Datensatzes, generiert aus dem output.schema in der manifest.json.
| Feld | Fachlicher Name | Typ | Beispiel | Beschreibung |
|---|---|---|---|---|
| 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 |
Datensatz-Schema
Die Ausgabe wird Datensatz für Datensatz zurückgegeben. 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
}Integration
Diese App kann über MCP, API, SDK oder Dateiexport integriert werden — alle Kanäle teilen sich dieselben Fähigkeiten und Preise. Jede Anfrage authentifiziert sich über den Authorization: Bearer-Header mit einem API Key (langlebig, in der Data Hub Konsole erstellt); MCP-Clients können sich zusätzlich per OAuth ohne Key anmelden. Weitere Optionen wie CLI und Skill sind in Vorbereitung.
Über das MCP (Model Context Protocol) können Sie diese App direkt aus KI-Clients wie Claude und Cursor aufrufen. Wählen Sie Ihren Client und den Authentifizierungsmodus und kopieren Sie dann die Konfiguration unten.
Client-Konfiguration
Ersetzen Sie den Wert nach Bearer durch Ihren langlebigen API Key. Funktioniert in jedem Client, in CI und in Headless-Umgebungen.
{
"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>" }
}
}
}Lassen Sie die KI die Einrichtung übernehmen
Sie möchten Konfigurationen nicht von Hand bearbeiten? Kopieren Sie den Installations-Prompt und fügen Sie ihn in einen beliebigen KI-Client ein — er schließt die Einrichtung auf seine eigene Weise ab. (Der Prompt weist die KI an, Ihren API Key bei Ihnen zu erfragen, damit Zugangsdaten nie im Chatverlauf oder in geteilten Konfigurationen landen.)
detail.access.mcp.composeHint
Preise
Wird pro übermitteltem Lauf einmal berechnet, unabhängig davon, wie viele Datensätze zurückgegeben werden.
Berechnet nach der Anzahl der erfolgreich zurückgegebenen Datensätze. Fehlgeschlagene Läufe werden nicht berechnet.
Mehrere Abrechnungsereignisse werden unabhängig voneinander kumuliert. Details siehe jeweilige Position. Fehlgeschlagene Läufe werden nicht berechnet.
Credits ansehenJetzt ausprobieren
Füllen Sie die Parameter aus und starten Sie — die Ergebnisse stammen aus einem echten Aufruf.