Skip to main content
Glama
KalpeshMahida0212

runsheet-mcp

by KalpeshMahida0212
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Free YouTube thumbnail maker

runsheet_make_thumbnail
Read-only

Generate a YouTube thumbnail PNG from a headline and layout to provide separate 16:9 and 9:16 URLs for long cuts and Shorts.

Instructions

Render a YouTube thumbnail as a PNG from a headline and a layout. Returns a URL for the 16:9 version used by long cuts and the 9:16 version used by Shorts, which are different files on YouTube and cannot be substituted for each other.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artNoOptional. An art id from runsheet_draw_thumbnail_art, to use as the background. Anything that is not one of those ids is ignored and the thumbnail renders on its plain ground.
footNoA short concrete detail along the bottom.
toneNobad is red and for a problem, good is green and for an answer, neutral is gold.
brandNoChannel name, along the very bottom.
kickerNoThe small line above the headline.
layoutNostatement: A flat claim in the largest type that fits. The workhorse; start here. question: The headline as the thing the viewer is already wondering, with the mark oversized. number: A numeral doing the work. For counts, lists, days, and anything with a figure in it. band: Type in a solid band across the lower third. The highest contrast option.
headlineYesThree or four words, upper case or not. This is the whole thumbnail.
highlightNoComma separated words inside the headline to set in the accent colour.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already covering the safety profile, the description adds genuinely useful behavioral context: the return value is a URL, two aspect-ratio files are produced, and they are non-interchangeable on YouTube. It stops short of covering failure modes or what happens when layout is omitted.

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?

Two sentences, zero waste, front-loaded with the action and result before the caveat. Every clause earns its place.

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?

For an 8-parameter rendering tool with no output schema, the description supplies the missing return-shape information (URLs, two aspect ratios) that an agent otherwise could not infer. Minor gap: it does not say what layout is used when the optional layout parameter is omitted.

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 description coverage is 100%, so every parameter including the enum vocabularies for tone and layout is already fully documented in the schema. The description only names headline and layout as the drivers, adding nothing the schema does not already say.

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 output ('Render a YouTube thumbnail as a PNG') plus the two inputs it is driven by (headline, layout), and distinguishes itself from every sibling, which are all get/list/upload/style tools. The 16:9 vs 9:16 output split further pins down exactly what this produces.

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

Usage Guidelines3/5

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

Usage is implied by the purpose but never stated: there is no 'use this when...' or 'do not use this for...' clause, and no named alternative or prerequisite. The relationship to runsheet_draw_thumbnail_art only appears in the schema, not the description.

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

Deploy Server

Other Tools