Skip to main content
Glama

search_space_videos

Search for space-related videos and retrieve MP4 playback URLs, with optional poster images and adjustable result limits.

Instructions

宇宙関連の動画(打ち上げ・ミッション映像・解説など)を検索し、再生用MP4 URLを返す。

content には表示用サマリ+ポスター画像(インライン)を返し、
structuredContent にはJSON(タイトル/再生URL/解像度別URL/字幕など)を返す。
動画自体は巨大なのでbase64埋め込みせず、クライアント/LLMがURLから再生する。

例: 「火星の動画」「ロケット打ち上げ映像」「ハッブルの映像」

Args:
    query: 検索語(mars, launch, hubble, artemis など英語が確実)。
    limit: 返す動画件数(既定 3、最大 10)。
    show_poster: ポスター画像をチャットにインライン表示するか(既定 True)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
show_posterNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Explains the return behavior in detail: content includes a summary and inline poster, structuredContent includes JSON with title/play URL/resolution/subtitles, and large video data is never base64-embedded but played from URL. This is meaningful behavioral disclosure beyond basic search semantics.

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?

Description is well-structured with a clear summary, return-format explanation, examples, and an Args list. Every sentence adds value and no redundant filler is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description explains what appears in content and structuredContent, including key fields and the URL-based playback approach. Examples and parameter constraints together give an agent enough context to call and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters are described in the text even though the schema has no descriptions. Query semantics, English reliability, limit constraints (default 3, max 10), and show_poster behavior are all explicitly stated.

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?

Description clearly states the tool searches space-related videos and returns playable MP4 URLs. It gives concrete usage examples (Mars, rocket launch, Hubble) and distinguishes itself from sibling tools like search_space_images and search_space_audio by focusing on video content.

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?

Provides practical guidance such as using English query terms for better results and notes the default/maximum limit. It does not explicitly contrast with sibling tools or state when not to use it, but the resource type and examples make the appropriate usage clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/loosephoto/space-finder-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server