Skip to main content
Glama

send_video

Send an MP4 video from a URL, local path, or base64 to a QQ friend, group, or chat target, with an optional cover image.

Instructions

Send a video (mp4 from URL, path or base64).

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": {
      "target": "<target>",
      "file": "<file>"
    },
    "name": "send_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesURL / path / base64 of the video
thumbNoOptional cover image
targetYesWho to talk to: "qq:<QQ号>" for a friend/private chat, "group:<群号>" for a group, a bare number, or a friend remark/nickname/group name (must be unambiguous).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already disclose this is a non-read-only, non-destructive, open-world send operation, so the safety profile is covered. The description adds the accepted input encodings but says nothing about size/duration limits, delivery failure behavior, or whether the video is re-hosted. Useful but thin for a media-message send.

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 compact sentence with the format-and-source information front-loaded and no filler. It is efficient, though the parenthetical makes it read slightly like a schema restatement.

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

Completeness3/5

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

With only three well-documented parameters, no output schema, and annotations present, the essentials are covered. What's missing is the practical envelope for sending video: size constraints, whether thumb must match a specific format, and how failures surface.

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%, including detailed target routing syntax, so the schema does the heavy lifting and baseline 3 applies. The description only adds the 'mp4' format constraint, which is mild added value.

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?

A specific verb+resource ("Send a video") plus the accepted source formats (mp4 from URL, path, or base64) tells the agent exactly what the tool does. It doesn't distinguish itself from near neighbors like send_file or upload_video_to_qun_album, so it stops short of a 5.

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?

The description gives no when-to-use guidance and no exclusions, despite a crowded family of send_* tools where an agent must choose between sending a video as a message, as a file, or uploading it to a group album. The agent is left to infer that this is the plain message-send path.

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

Deploy Server

Other Tools