Skip to main content
Glama

玩具品牌官方 YouTube 頻道最新新品介紹影片

toys__official_toy_videos
Read-onlyIdempotent

[NEW玩具情報站]玩具品牌官方 YouTube 頻道最新新品介紹影片(Good Smile、BANDAI SPIRITS、壽屋、TAKARA TOMY、POP MART、Funko、Hasbro Pulse、Mattel、LEGO、PLAYMOBIL 等)。

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

Input Schema

NameRequiredDescriptionDefault
zoneNo
brandNo品牌名稱
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered structurally. Beyond that, the description only adds the brand coverage list; it says nothing about how 'latest' is determined (recency window, ordering), how many videos come back, or whether results are cached or scraped live from open web sources.

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?

A single sentence with the resource front-loaded and no filler or repetition of the title beyond the bracketed section label. The parenthetical brand list is long but earns its place as coverage scope, so the description is tight rather than padded.

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

Completeness2/5

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

For a three-parameter open-world retrieval tool with no output schema and only 33% schema coverage, the description should say something about result shape, ordering, or how zone/limit behave. It covers only brand coverage, so an agent still cannot predict what a call returns or how to constrain it.

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?

Schema coverage is only 33% — only 'brand' carries a description ('品牌名稱'). The description implicitly explains what 'brand' means by listing brand names, but it says nothing about 'zone' (an enum of 亞洲/美國/歐洲) or 'limit', leaving two of three parameters without added meaning. Since all parameters are optional and one enum is self-describing, the gap is not fatal but it is real.

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 states a concrete resource: latest new-product introduction videos published on official toy brand YouTube channels, and enumerates the covered brands (Good Smile, BANDAI SPIRITS, LEGO, etc.). An agent can tell this is a video-feed tool rather than a news or product-lookup tool, though it never explicitly contrasts itself with siblings such as toys__official_toy_news or games__official_game_trailers.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — no statement of when to pick this over toys__official_toy_news, toys__latest_toy_news, or games__official_game_trailers. The description also never mentions the zone or limit filters, so an agent gets no hint about how to narrow results or when filtering is appropriate.

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