Skip to main content
Glama
Hsky16

yahoo_realtime_search

by Hsky16

search_realtime

Retrieve recent posts from Yahoo! Real-time Search with filters for query, sort order, media type, and date range.

Instructions

Yahoo!リアルタイム検索で最近の公開投稿を検索します。

現在の反応、トレンド、ハッシュタグ、アカウント指定検索、日本語圏の話題、 画像や動画付き投稿を探すときに使います。一般的な Web 検索や公式情報の確認には 使わないでください。

主な引数:

  • query: 検索語です。"#hashtag", "-word", "A OR B", "ID:username", "@username", "URL:domain" などの検索演算子も使えます。

  • sort: "latest" は新着順、"popular" は反応が多い投稿を優先します。

  • media_type: "image", "video", "all" を指定できます。標準は "image" です。

  • limit: 1 ページあたりの件数です。1 から 40 まで指定できます。

  • pages: 取得するページ数です。1 から 25 まで指定できます。ページ数が増えるほど API へのリクエストも増えます。

  • start: 取得開始位置です。

  • since / until: Unix 秒、または ISO 8601 形式の日時を指定できます。

  • output_format: 標準は "markdown" です。構造化データが必要なときは "compact_json"、詳しい整形済みデータが必要なときは "full_json"、元 API の レスポンス確認には "raw_json" を使います。

Markdown 出力の構造:

  • H1 に検索語を表示します。

  • 先頭の箇条書きに取得件数、推定総件数、検索条件を表示します。

  • 投稿ごとに H3 を作り、著者、ISO 形式の投稿時刻、反応数、投稿リンクを表示します。

  • 投稿本文は Yahoo 側の displayTextBody/displayText 由来で、引用として表示します。

  • 外部リンクは Markdown の箇条書きで表示します。タイトルがある場合は title、 ない場合は display URL または URL を使います。

  • メディア URL はラベルを繰り返さず、通常の箇条書きで表示します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
sortNolatest
media_typeNoimage
limitNo
pagesNo
startNo
oldest_tweet_idNo
sinceNo
untilNo
output_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully covers behavioral aspects: it searches Yahoo! real-time search, returns posts in multiple formats, explains output structure, notes that increasing pages increases API requests, and details parameter effects. No contradictions or missing critical traits.

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 well-structured: header with purpose, then parameter list, then output format details. It is slightly long but every sentence is informative. Front-loaded with key info. Could be slightly more concise, but still highly effective.

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?

Given the tool's complexity (10 parameters, multiple output formats, detailed output structure), the description is complete. It covers use cases, parameter details, output format, and internal behavior. Although an output schema exists, the description still adds value by explaining the Markdown structure.

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?

Schema coverage is 0%, so the description must add meaning. It does so comprehensively, explaining each parameter (query with operators, sort, media_type, limit, pages, start, since/until, output_format) with examples and context. This far exceeds baseline expectations.

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?

The description explicitly states the tool's purpose: searching recent public posts using Yahoo!リアルタイム検索, with specific use cases (reactions, trends, hashtags, accounts, Japanese topics, images/videos) and explicit exclusion (general web search, official info). This is a specific verb+resource with clear differentiation from potential alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on when to use the tool (real-time search for recent posts) and when not to (general web search, official info). It also explains parameters and their intended use, giving the agent sufficient context to decide.

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

Install Server

Other Tools

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/Hsky16/yahoo_realtime_search'

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