benchmark_channel

Benchmark a YouTube channel against its niche — engagement percentiles, title patterns, and exemplar channels.

MCP benchmark_channel 5 credits REST equivalent: POST /v1/benchmark/channel

REST vs MCP response shape

MCP tool responses include two extra fields that the REST endpoint does not return:

score_id — an immutable identifier for the call, useful for client-side correlation and replay.
credits_remaining — your balance after this call. REST clients fetch the balance via GET /v1/usage/.

benchmark_channel and benchmark_video additionally wrap the response body under a payload field, so the envelope is {score_id, credits_remaining, payload}. The other tools merge the fields at the top level.

This is intentional. Tool-using agents typically want both pieces of state inline; HTTP clients usually do not.

Parameters

Parameter	Type	Description
url required	string (≤1024 chars)	Channel URL or @handle. Accepts /@handle, /channel/UC…, /c/<name>, /user/<legacy>.

Example call

Tool invocation via an MCP client (JSON arguments):

{
  "url": "https://www.youtube.com/@MarquesBrownlee"
}

Example response

{
  "score_id": "01J7K7...",
  "credits_remaining": 324,
  "payload": {
    "channel": {
      "channel_id": "UCBJycsmduvYEL83R_U4JriQ",
      "title": "Marques Brownlee",
      "subscriber_count": 18900000,
      "video_count": 1640,
      "engagement_percentiles": {
        "view_to_sub_ratio": 86,
        "like_to_view_ratio": 78,
        "comment_to_view_ratio": 62,
        "overall": 79
      },
      "sample_window_days": 90
    },
    "niche": {
      "slug": "tech-reviews",
      "name": "Tech Reviews",
      "match_score": 0.94,
      "match_strength": "strong"
    }
  }
}

Client setup

See Client setup for Claude Desktop and Cursor configuration. Once configured, ask your client to call benchmark_channel.