Skip to main content
Glama

Eurekuh

Set a YouTube post's thumbnail

set_youtube_thumbnail
Destructive

Give a YouTube post a custom thumbnail, before or after it is out. Once the video is live it is set as soon as YouTube accepts it (often only after processing), retried for about 7 hours. A new image replaces the old one. The channel must be verified for custom thumbnails; get_post_status shows the result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "thumbnail": "<thumbnail>"
    },
    "name": "set_youtube_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe YouTube post id from create_post or list_posts.
thumbnailYesA JPG or PNG mediaId from upload_file or upload_media. 9:16 suits a Short.
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: setting is asynchronous once live, resolution depends on YouTube acceptance/processing, retries persist for roughly 7 hours, and an existing thumbnail is replaced. It also discloses the verified-channel precondition, which the annotations do not imply. The replacement semantics are consistent with destructiveHint=true and nothing contradicts idempotentHint=false.

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

Conciseness5/5

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

Four sentences, each doing distinct work: purpose and timing, async/retry behavior, replacement semantics, precondition plus verification path. The most decision-relevant facts (what it does, when it can be done) are front-loaded with no filler.

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

Completeness4/5

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

With no output schema and a mutation that completes asynchronously, the description correctly supplies the verification route (get_post_status) and the retry horizon. The only modest gap is that it does not say what the immediate call returns, but the sibling pointer largely compensates.

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

Parameters3/5

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

Schema coverage is 100%, with the id, thumbnail format/source, aspect-ratio hint, and organizationId fallback all documented in the schema itself. The description adds only the behavioral note that a new image replaces the old one, which is not parameter-level meaning. Baseline 3 applies when the schema carries the load.

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

Purpose5/5

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

States a specific verb and resource ('Give a YouTube post a custom thumbnail') and scopes it by timing ('before or after it is out'). This is inherently distinguishable from upload_file/upload_media (which produce the image) and from get_post_status (which is explicitly named as the result-checking sibling).

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 gives clear operating context: usable both before publish and post-publish, requires a verified channel, and directs the agent to get_post_status to confirm the outcome. It stops short of explicit exclusions ('do not use for X, use Y instead'), so it is not a full when/when-not treatment.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources