score_packaging

Score a YouTube packaging (title and/or thumbnail) for predicted click-through rate. The server auto-detects mode from your inputs.

MCP score_packaging 1 / 2 / 3 credits REST equivalent: POST /v1/score/packaging

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
title	string (≤250 chars)	Video title. At least one of title / thumbnail_url / thumbnail_base64 is required.
thumbnail_url	url (≤1024 chars)	Public URL to a JPG/PNG/WebP image. Mutually exclusive with thumbnail_base64.
thumbnail_base64	string (≤12.5 MB encoded)	Base64-encoded image. Mutually exclusive with thumbnail_url.
channel_url	url	Reserved — currently accepted but not consumed by the model.

Example call

Tool invocation via an MCP client (JSON arguments):

{
  "title": "10 Tips to Boost Your Coding Productivity",
  "thumbnail_url": "https://i.ytimg.com/vi/abc123/maxresdefault.jpg"
}

Example response

{
  "score_id": "01J7K4...",
  "score": 0.81,
  "percentile": 81,
  "raw_score": 1.42,
  "mode": "combined",
  "niche_slug": "tech-tutorials",
  "niche_label": "Tech Tutorials",
  "niche_confidence": 0.93,
  "credits_remaining": 344
}

Client setup

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