Dynamoi

Get YouTube Channel Data

dynamoi_get_youtube_channel_data

Read-only

Use this for "how is my YouTube channel doing?" or "what is growing my channel?" once a channel is linked. Use this to analyze an artist's own connected YouTube channel's estimated ad revenue to inform AdSense strategy and channel growth, alongside subscribers, views, watch time or country, device and subscribed-status breakdowns: paged channel data from the YouTube Analytics warehouse or explicitly qualified synthetic/sample data. Pick one dataset: channel_daily (views, watch time, subscribers gained and lost, likes, shares, playlist starts, estimated revenue, ad revenue, gross revenue, monetized playbacks, CPM and playback-based CPM), video_daily (per-video metrics with titles; filter with videoIds), country_daily, traffic_source_daily, search_term_daily (YouTube search terms for the whole channel), subscribed_status_daily, device_daily, operating_system_daily, playback_location_daily, creator_content_type_daily, or video_catalog (video titles and publish dates). traffic_source_daily rows with source ADVERTISING carry trafficClass=paid and every other source carries trafficClass=organic, but that label only groups sources and is not organic proof: ad clicks that land in a playlist are credited mostly to PLAYLIST and SUBSCRIBER, so trafficClass=organic rows include ad sessions. Organic lift is growth in sources ads do not touch (YT_SEARCH, RELATED_VIDEO, browse features) or lift that persists after spend stops. Warehouse data is observed on the channel, not attributed to any campaign. Preserve the returned source, coverage, freshness, and synthetic/sample qualifications; do not treat synthetic/sample data as observed channel results, campaign attribution, or actual earnings/payouts. Treat returned ad revenue as estimated revenue, not an AdSense payout. The first page of any dataset (including format=summary) also carries one adsense block, the same figures the Dynamoi dashboard and app show: formats (long-form versus Shorts AdSense revenue and RPM), recovery and campaigns (incremental AdSense since each campaign and whether it earned back the billed amount), and countries (AdSense per ad playback against similar channels). It is estimated, not a payout, and covers windowFromDay to windowThroughDay, which is not always the requested range: compare against those fields. recovery.state building or unavailable and null figures mean unknown, never zero; adsense is null outside the YouTube Partner Program, on later pages, or when temporarily unavailable (adsenseNote explains). Compare periods yourself and use the campaigns block (dates, strategy, promoted videos) as context. YouTube data arrives about 2-3 days late and revenue can lag further: check coverage before comparing, and treat placeholderDays and missingDays as unknown, never zero. Not available yet: audience demographics, per-video traffic sources and per-video search terms. Needs a connected channel; a channel that must be reconnected is refused. Returns no ad spend. Before judging a campaign's strategy, read the strategyGuide from dynamoi_get_campaign. Page with nextCursor; format=summary returns only the summary, coverage and adsense.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`format`	No
`dataset`	Yes
`endDate`	Yes
`artistId`	Yes
`videoIds`	No
`startDate`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`data`	No
`kind`	No
`field`	No
`status`	Yes
`draftId`	No
`message`	No
`retryable`	No
`nextAction`	No
`failureStage`	No
`prerequisite`	No
`screeningResult`	No
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / properties / code / enum

Previous value: -[
-  "ACCOUNT_READ_ONLY",
-  "INVALID_SPOTIFY_SOURCE",
-  "CAPABILITY_REQUIRED",
-  "INSUFFICIENT_SCOPE",
-  "STATE_CONFLICT",
-  "QUOTE_CHANGED",
-  "RATE_LIMITED",
-  "OUTPUT_INVALID",
-  "UNKNOWN_EFFECT"
-]New value: +[
+  "ACCOUNT_READ_ONLY",
+  "INVALID_SPOTIFY_SOURCE",
+  "CAPABILITY_REQUIRED",
+  "INSUFFICIENT_SCOPE",
+  "TENANT_ACCESS_DENIED",
+  "STATE_CONFLICT",
+  "QUOTE_CHANGED",
+  "RATE_LIMITED",
+  "OUTPUT_INVALID",
+  "UNKNOWN_EFFECT"
+]

AddedSep 28, 2026

TDQS

A4.1/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, but the description adds substantial behavioral context: estimated revenue versus AdSense payout, 2-3 day data latency, revenue lag, unknown versus zero semantics for placeholderDays/missingDays/recovery.state, adsense null conditions, synthetic/sample qualifications, and the fact that no ad spend is returned. This is unusually rich non-contradictory disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single massive paragraph with no headers, bullets, or visual separation. Important caveats about latency, null handling, and prerequisites are buried after long dataset enumerations, making it costly for an agent to parse despite much of the content being substantive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complex tool with 8 parameters, no schema descriptions, an output schema, and annotations, the description is highly complete. It covers dataset semantics, freshness caveats, null semantics, prerequisites, and limitations, while the output schema can handle return-value documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must carry parameter meaning. It does well for the dataset enum by listing each dataset's metrics, explains videoIds filtering for video_daily, format=summary behavior, cursor pagination via nextCursor, and implies date-range mapping through windowFromDay/windowThroughDay. It still leaves limit bounds and startDate/endDate mapping largely implicit, so it is strong but not complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as an artist's connected YouTube channel analytics and enumerates datasets and metrics, but it opens with example questions rather than a crisp verb+resource statement. It also does not explicitly name or distinguish sibling analytics tools such as dynamoi_get_audience_analytics or dynamoi_get_artist_analytics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use the tool ('how is my YouTube channel doing?' or 'what is growing my channel?'), gives key prerequisites (channel linked, reconnected channel refused), and names dynamoi_get_campaign for strategy context. However, it lacks systematic comparison against sibling analytics tools, so it falls short of full when/when-not/alternatives guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dynamoi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.