Skip to main content
Glama

get_video_detail

Fetch one Bilibili or Douyin video's details and a nine-frame grid for pre-curation review; if frame extraction fails, it returns visual.available=false to prevent guesswork.

Instructions

取单条材料和九宫格画面(MCP图片)。必须先查看再判定。抽帧失败会返回visual.available=false,不能编造人物或作品质量。

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": {
      "platform": "<platform>",
      "video_id": "<video_id>"
    },
    "name": "get_video_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes平台
video_idYesbvid 或 aweme_id
include_framesNo默认true;仅文字可显式false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that images are returned, that frame-extraction failure yields visual.available=false, and that fabricating people/quality is forbidden. Auth requirements and rate limits remain undisclosed, keeping it from a 5.

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?

Three short, front-loaded sentences: purpose first, then a workflow rule, then a failure/integrity caveat. No filler; each sentence carries weight, though the second and third could be marginally tighter.

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?

For a read tool with no output schema, the description covers the essential return shape (nine-grid image) and a key failure mode (visual.available=false). Nothing critical to correct invocation is missing, though the specific structure of the returned material is only sketched.

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 100%, so the schema already documents all three parameters including the include_frames default and platform enum. The description's mention of nine-grid frames loosely ties to include_frames but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource: fetch a single material plus a nine-grid frame (MCP image) for a given video. The retrieval nature is unambiguous, though it does not explicitly differentiate itself from siblings such as collect_video or submit_verdict beyond the 'view before judging' tie-in.

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?

'必须先查看再判定' supplies a workflow directive (inspect before forming a verdict), which is real usage context. However, it names no alternatives and gives no explicit when-not-to-use conditions, leaving it at implied rather than explicit guidance.

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