Skip to main content
Glama

숏츠생성기 Free K-pop Shorts

영상 찾기 / Search videos

search_videos
Read-onlyIdempotent

무료로 받을 수 있는 완성 쇼츠 영상을 찾습니다(한 쪽에 12편, limit으로 1~50편). artist(아티스트 이름: 띄어쓰기나 대소문자가 달라도, 이름의 일부여도, 영어 이름 같은 다른 이름이어도 한 팀으로 정해지면 그 팀), query(제목·아티스트·태그 검색어), page(1부터)로 거를 수 있습니다. 받기 링크와 설명은 get_video로 받으세요. Searches the free, finished YouTube Shorts (12 per page; limit sets 1 to 50) by artist name (spacing and letter case are ignored; part of a name or another name of the artist, such as its English name, is enough when it points to one artist), a title/artist/tag keyword and page; call get_video for the download link, title and description.

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

Input Schema

NameRequiredDescriptionDefault
pageNo쪽 번호(기본 1) / page number, default 1
limitNo한 쪽에 받을 편수(1~50, 기본 12) / videos per page, 1 to 50, default 12
queryNo제목·아티스트·태그에 들어 있는 말 / keyword contained in the title, the artist or a tag
artistNo아티스트 이름(list_artists의 이름이나 aliases. 조금 달라도 한 팀으로 정해지면 그 팀으로 찾음) / artist name or alias from list_artists (a close or partial name is used when it points to one artist)

Output Schema

NameRequiredDescriptionDefault
pageYes
itemsYes
pagesYes
queryNo검색어 / keyword
totalYes
artistNo거른 아티스트(라이브러리의 이름) / artist filter (the name in the library)
noticeNoartist를 검색어로 바꿔 찾았을 때의 안내 / set when the artist given was searched as a keyword instead
next_pageYes다음 쪽 / next page
page_sizeYes
browse_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value beyond them by disclosing the corpus restriction to 'free, finished' shorts, the 12-per-page default with a 1-50 limit, and the fuzzy artist-matching rule (spacing, case, partial, or alias names resolving to one team).

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 purpose and pagination constraints are front-loaded, and the get_video handoff closes the block. It is somewhat longer than needed because the entire content is duplicated in Korean and English, but the duplication appears deliberate for language coverage rather than padding.

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, the description need not explain return values, and it correctly defers to get_video for link and description fields. Coverage of scope, all four optional filters, and pagination is solid; the only minor gap is the absence of any statement about result ordering.

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 baseline is 3, but the description goes further on artist by spelling out that spacing and letter case are ignored, that a partial name suffices, and that an alternate/English name mapping to one team is accepted. It also restates page 1-based indexing and the limit range in prose, adding modest reinforcement.

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 ('Searches the free, finished YouTube Shorts') and pins the scope with default page size and the limit range. It also clearly demarcates the sibling boundary by directing the agent to get_video for download links, titles, and descriptions.

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?

Gives clear context for when this tool is the right one: browsing free, finished shorts by artist, keyword, and page, with an explicit handoff to get_video for the actual download link and metadata. It does not state explicit exclusions or a when-not case, so it falls short of full alternative routing.

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