Skip to main content
Glama

ENTERADS Free Shorts Library

아티스트 목록 / Artists

list_artists
Read-onlyIdempotent

엔터애즈 무료 쇼츠 라이브러리에 지금 받을 수 있는 영상이 있는 아티스트와 아티스트별 영상 수를 보여 줍니다. Lists the artists that currently have free, ready-to-upload YouTube Shorts in the ENTERADS library, with the number of videos each.

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds real behavioral context beyond them: the result set is filtered to artists with currently downloadable videos and is dynamic over time, which tells the agent not to expect a full artist catalog. It does not state ordering or whether counts are totals.

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?

Two sentences, front-loaded with the resource and scope, with no filler. The Korean and English statements are mirror translations rather than new information, which is mild redundancy but appropriate for a bilingual tool title.

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 an output schema present and annotations declaring the read-only, closed-world safety profile, the description need only establish what the listing is and how it is scoped, which it does. Minor gaps remain around result ordering and result size, but nothing prevents correct invocation.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description adds no parameter information, and none is needed.

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 names a specific verb and resource ('Lists the artists') and narrows scope to those 'that currently have free, ready-to-upload YouTube Shorts in the ENTERADS library,' plus the returned aggregate ('number of videos each'). This is far more precise than a bare resource name and implicitly separates it from video-level siblings like get_video and search_videos, though no sibling is named explicitly.

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?

The phrase 'currently have free, ready-to-upload' implies the tool is the entry point for browsing downloadable content by artist, but there is no explicit when-to-use or when-not statement and no reference to alternatives such as search_videos. Usage is inferable rather than stated.

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