Skip to main content
Glama
Sign In

LetsBot

by net.letsbot
OverviewDiscussionsAdmin

send_video

Destructive

Send a video to a WhatsApp number with an optional caption.

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": {
      "phone": "<phone>",
      "video_url": "<video_url>",
      "confirm": "<confirm>"
    },
    "name": "send_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesWhatsApp number in international format without + (e.g. 201234567890), or the contact's phone / chat_id as listed by get_conversations_awaiting_reply (website chat, Messenger, Instagram, Telegram…)
captionNoOptional caption for the video
confirmYesConsent gate — REQUIRED on every call. Pass false first: the tool then performs no action and returns a preview of exactly what would happen. Show that preview to the user, get their explicit approval, and only then call again with true to send this video.
video_urlYesURL of the video to send

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered structurally; the description adds nothing about irreversibility, rate limits, or the two-step confirm flow. It is consistent with the annotations but essentially restates the name plus 'optional caption', contributing no behavioral context of its own.

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 front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of omitting the confirm gate and message-delivery behavior.

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?

This is an irreversible outbound message tool with no output schema, and the description never mentions the mandatory confirm-then-preview handshake, delivery failure modes, or how it relates to the other send_* tools. The schema carries the critical detail, but the description leaves real gaps for an agent deciding how to call 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 description coverage is 100%, including the detailed confirm consent gate and phone format, so the schema does all the work. The description's only parameter note ('optional caption') merely repeats what the schema already says, making 3 the correct baseline.

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 and resource (send a video) plus the medium, which implicitly distinguishes it from siblings like send_image, send_audio, and send_file. It doesn't name any sibling or explain the boundary with send_file (which can presumably also carry media), so it falls 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?

There is no guidance on when to use this versus send_file, send_image, or reply_to_message, and no mention of the required confirm/preview workflow that governs every call. The agent must discover the consent gate entirely from the schema.

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

All LetsBot toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources