Skip to main content
Glama

숏츠생성기 Free K-pop Shorts

영상 받기 정보 / Get video

get_video
Read-onlyIdempotent

영상 한 편의 받기 링크(download_url), 그대로 붙여 넣을 제목과 설명(자료 제공 줄과 영상 코드 줄 포함), 썸네일을 줍니다. 설명은 고치거나 줄이지 말고 그대로 쓰세요. Returns one video's download link, the title and the ready-to-paste description (it contains a source line and the video's EAV- code; keep both unchanged), the thumbnail and usage notes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video_id": "<video_id>"
    },
    "name": "get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYessearch_videos가 준 video_id / video_id from search_videos

Output Schema

NameRequiredDescriptionDefault
codeYes영상 코드 / video code
titleYes
artistYes
creditYes자료 제공 / source credit
video_idYes
duration_sYes
descriptionYes
usage_notesYes
download_urlYes
needs_signupYes
source_titleNo원본 영상 제목(참고) / title of the video this cut was made from (reference only)
download_modeYes
scene_summaryNo영상에 담긴 장면(영상을 고를 때 참고, 붙여 넣는 글이 아님) / what the scene shows (for choosing a video; not part of the text to paste)
thumbnail_urlYes썸네일 / thumbnail
video_page_urlYes
direct_downloadYestrue = download_url은 원본 파일 / the original file; false = 영상 페이지 / the video page
source_publishedNo원본 영상 공개일 YYYY-MM-DD / day the source video was published

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds the non-obvious fact that the returned description embeds a source line and an EAV- code that must stay unchanged. That is real behavioral context beyond structured fields. It doesn't discuss rate limits or failure cases, which is acceptable for a read-only lookup.

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 description is front-loaded with the returned artifacts and then the key constraint about the description field. The Korean and English halves are largely redundant, which slightly inflates length, but the 'keep unchanged' warning is repeated usefully rather than wastefully. No filler sentences.

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?

An output schema exists, so return values needn't be enumerated in prose, and the description still flags the one risky field (description containing source and code lines). For a single-parameter, read-only lookup this is nearly complete. Explicit when-to-use guidance relative to search_videos is the only missing piece.

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?

There is only one parameter, and the schema describes it at 100% coverage, including a regex pattern and a note pointing to search_videos. The description adds no further meaning about video_id. This is the expected baseline when the schema does the work.

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: it returns exactly one video's download link, title, ready-to-paste description, thumbnail, and usage notes. It also states the scope ('영상 한 편의' / 'one video's'), which separates it from a list or search tool. It doesn't explicitly name search_videos as the intended feeder tool, though the schema does.

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 guidance is limited to how to handle the output ('설명은 고치거나 줄이지 말고 그대로 쓰세요' — don't edit or shorten the description). There is no explicit statement of when to call this rather than search_videos or list_artists; the workflow of getting a video_id from search_videos appears only in the schema's parameter note.

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