logo
languageENdown
menu

YouTube Account Info

Collect public channel profiles, audience metrics, and contact signals for one or more YouTube accounts

Overview

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.

Scope and boundaries

Each run accepts 1 to 200 YouTube accounts or channel names and returns public profile records when data is available.

  • Good for
  • 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
  • Do not use for
  • 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

Failure handling

Failure and retry behavior declared by the author. We recommend including it in your system prompt when integrating.

  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

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

FieldBusiness nameTypeRequiredDefaultEnum / ConstraintsExampleDescription
itemsYouTube account listarray<object>Yes—up to 200 items[{"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.

Output

Field structure of a single record, generated from the output.schema in manifest.json.

FieldBusiness nameTypeExampleDescription
task_itemSubmitted accountstringUlanziJapanThe account or channel name submitted for this record
no_dataNo databooleanfalseWhether this submitted account returned no public profile
keywordSource keywordstringUlanziJapanThe source keyword associated with the collected account
account_idChannel IDstringUCUo0_zutHjxAwHnrTHFph_gThe YouTube channel identifier returned for the profile
account_nameChannel namestringUlanzi Japan(ウランジ)The displayed YouTube channel name
account_home_urlChannel URLstringhttps://www.youtube.com/@UlanziJapanThe public YouTube channel URL
biz_idBusiness IDstringUlanziJapanThe business identifier carried by the source profile record
emailPublic emailstring—The contact email shown on the public channel profile when available
fans_countFollower countstring—The displayed follower count retained as source text
fan_nums_originRaw follower textstring—The original follower-count text supplied by the source
locationLocationstring—The location text displayed on the channel profile
countryCountrystring—The country text displayed on the channel profile
joined_dateJoined datestring—The channel joined date as displayed by the source
linksProfile linksstring[]Public profile links retained as source text
views_numView countstring—The displayed total view count retained as source text
publish_content_countVideo countstring—The displayed public video or content count retained as source text
clean_update_timeSource updated atstring2026-08-27T14:19:57The source timestamp when the profile data was updated
crawl_timeCollected atstring2026-08-27T14:19:57The source timestamp when the channel profile was collected

Record schema

Output is returned record by record. detail.output.idFieldHint

output.schema
{
  "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

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "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>" }
    }
  }
}

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (The prompt asks the AI to request your API key from you, so credentials never end up in chat history or shared configs.)

detail.access.mcp.composeHint

Pricing

Task start

Charged once per submitted run, regardless of how many records are returned.

$0.0001/ run
Returned profile

Charged by the number of records successfully returned. Failed runs are not charged.

$0.0004/ record

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
Please fill in the required parameters first
From $0.0004 / record