Skip to main content
Glama

Image size for a streaming platform

get_image_size
Read-onlyIdempotent

Exact recommended pixel size, aspect ratio, file limits, formats and design tips for streamer images: Twitch emotes, badges, panels, banners, offline screen, profile picture and overlay; YouTube banner, thumbnail and profile picture; Discord emoji, sticker, banner, server icon and avatar; Kick banner; TikTok profile picture; X header. Specs were checked against each platform in October 2026. Pass "asset" for one answer, or only "platform" to list every size for that platform.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_image_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoThe image, e.g. "twitch emote", "youtube thumbnail", "discord sticker", "kick banner".
platformNoOptional platform filter. With no "asset", lists all sizes for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuinely new behavioral context: the data is a curated static snapshot, "checked against each platform in October 2026", which tells the agent results will not reflect later platform changes. It does not say whether results are cached or how large a platform listing response is.

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?

Purpose and coverage are front-loaded, and the platform/asset enumeration, though long, is load-bearing because it defines the tool's scope. The closing sentence delivers the call pattern without any 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?

For a zero-required-parameter lookup with no output schema, the definition covers scope, data currency and call modes well. The one omission is the no-argument case: nothing says whether an empty call is an error, returns everything, or is meaningless.

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?

Schema coverage is 100%, so both parameters are already documented, and the baseline would be 3. The description earns an extra point by specifying the combination semantics that the schema only half-states: asset alone yields one answer, platform alone yields a full listing, clarifying the interaction between the two optional fields.

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 concrete resource (image specs: pixel size, aspect ratio, file limits, formats) and enumerates the covered platforms and assets precisely. An agent can tell instantly that this is a static reference lookup rather than a live account call, and it does not overlap any sibling tool such as get_stream_settings or create_obs_widget.

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?

The final sentence gives explicit invocation guidance: pass "asset" for a single answer, or only "platform" to list every size for that platform. It does not mention what happens with no arguments or any case where this tool is the wrong choice, but the two supported modes are unambiguous.

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