Skip to main content
Glama

Baixar vídeo sem marca d'água

download_video
Read-only

Downloads a Shopee Video or TikTok video without watermark. Returns a direct MP4 URL and, for Shopee, the original caption with hashtags. Accepts share links like https://br.shp.ee/..., https://sv.shopee.com.br/share-video/... or https://vm.tiktok.com/....

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": {
      "url": "<url>"
    },
    "name": "download_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesShopee Video or TikTok share link. Extra text around the link is ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds meaningful behavior: watermark removal, direct MP4 return, and Shopee-specific caption output. It does not cover failure modes or URL expiration, but it adds useful context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three efficient sentences, front-loading the core action and following with return behavior and accepted input formats. Every sentence adds useful information without repetition.

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?

For a simple one-parameter read-only tool with no output schema, the description covers platform scope, accepted input formats, watermark removal, and returned values. No critical information needed to invoke the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents the single url parameter and notes that extra text is ignored. The description adds concrete example share-link patterns for Shopee and TikTok, which helps the agent recognize valid inputs.

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 states a specific verb and resource: downloads Shopee Video or TikTok videos without watermark. It also identifies the platform scope and return format, making the tool’s purpose immediately clear.

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?

Usage is implied by the supported platforms and accepted share-link formats, but the description does not explicitly say when to use this tool versus alternatives such as get_quota. It also gives no guidance on unsupported or invalid inputs.

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