Skip to main content
Glama

숏츠생성기 Free K-pop Shorts

아티스트 목록 / Artists

list_artists
Read-onlyIdempotent

숏츠생성기 무료 쇼츠 라이브러리에 지금 받을 수 있는 영상이 있는 아티스트와 아티스트별 영상 수를 보여 줍니다. 다른 이름(영어 이름 등)이 있으면 aliases에 함께 줍니다. Lists the artists that currently have free, ready-to-upload YouTube Shorts in the videocreate.kr library, with the number of videos each and, when an artist has them, the other names it goes by (aliases, e.g. its English name).

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": "list_artists"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
artistsYes
browse_urlYes
total_videosYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that, the description discloses meaningful behavior the annotations do not: results are filtered to currently available, free, ready-to-upload videos rather than all artists, and aliases are included only when they exist. It does not mention ordering, pagination, or whether artists with zero available videos appear.

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

Conciseness4/5

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

The content is front-loaded with the core behavior and is short overall. The main inefficiency is that the Korean and English sentences mirror each other almost verbatim, effectively doubling length, though that serves a bilingual audience rather than adding 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 zero parameters, complete annotations, and an output schema that carries the return shape, the description only needs to convey scope and filtering semantics — which it does, including the free/ready-to-upload constraint and the aliases caveat. Minor gaps remain around result ordering and whether artists without available videos are excluded or shown with a zero count.

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?

The tool takes zero parameters, so the baseline is 4 and the description correctly spends no words on argument meaning. It instead clarifies what the implicit implicit scope of the call is (only artists with currently downloadable free Shorts) and what the alias field represents, which is the useful semantic detail for a no-arg tool.

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

Purpose4/5

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

The description uses a specific verb and resource ('Lists the artists') and defines the population precisely: artists that currently have free, ready-to-upload YouTube Shorts in the videocreate.kr library. It also states what is returned (per-artist video counts and aliases), so the agent knows exactly what this tool yields, though it never names siblings like get_video or search_videos to sharpen the boundary.

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 only implied: the 'currently have free, ready-to-upload' framing suggests this is the discovery step before fetching or searching videos. There is no explicit 'use this when…' statement, no exclusion of when to prefer search_videos or get_video, and no prerequisite noted. Adequate to infer intent, but the agent must do the inferring.

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