Skip to main content
Glama
brilliant-directories-mcp

brilliant-directories-mcp

Official

getStockVideo

Read-onlyIdempotent

Fetches ready-to-use mp4 URLs from Pexels video pages for background videos, returning dimensions, orientation, file size, and playback guidance.

Instructions

Free stock video (mp4) for a background video. - Free stock video for a background, e.g. behind the homepage hero. Wrapper-native synthetic tool; does NOT proxy to BD. Give it Pexels video pages and it returns, for each, a ready-to-use mp4 url sized for a background (1280 wide when the video has that file), with width, height, orientation and size in mb, plus how to play it with no player buttons.

Find the pages with a web search for pexels free stock video <2-3 word topic>; they look like https://www.pexels.com/video/<name>-<id>/. A Pexels video link the owner gives works the same way. Pass several candidates in one call, then pick a landscape one for a wide background and prefer a smaller file.

Use when: the owner wants a background video and has not given a YouTube or Vimeo link.

Returns: { status, videos: [{ id, about, width, height, orientation, mb, url }], failed?, use }.

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": {
      "urls": "<urls>"
    },
    "name": "getStockVideo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes1 to 8 Pexels video pages (`https://www.pexels.com/video/<name>-<id>/`) or bare video ids, comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv6.59.638

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare read-only, idempotent, open-world, non-destructive, so the extra value here is the operational disclosure: it is a synthetic wrapper that does not proxy to BD, it downsizes to 1280 wide when that file exists, it surfaces width/height/orientation/mb, and it returns playback guidance for a buttonless player. Those are traits the annotations cannot express and they materially affect how an agent should call and trust it.

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

Conciseness3/5

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

The definition is front-loaded with the purpose and uses clear bold headers for 'Use when' and 'Returns', so it scans well. However, the opening is redundant — 'Free stock video (mp4) for a background video.' is restated almost verbatim in the next clause — and the dense mid-section packs source discovery, selection heuristics, and playback notes into one block, adding length that could be trimmed without losing meaning.

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?

There is no output schema, so the description carries the full burden of describing results, and it does: an explicit return shape listing status, videos with id/about/dimensions/orientation/size/url, an optional failed field, and a use field for playback. Combined with the sourcing and selection guidance, an agent has everything needed to call the tool and interpret what comes back.

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?

Schema coverage is 100% and the schema already documents the comma-separated Pexels page/id input with the 1-to-8 cap, so the baseline is 3. The description reinforces acceptance of bare ids and owner-supplied links and adds the batching strategy ('pass several candidates in one call'), which is genuine guidance beyond the schema, but the per-parameter meaning is largely already covered.

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 definition opens with a specific verb+resource (fetch a free stock video mp4 for a background) and immediately scopes the source: Pexels video pages, wrapper-native, explicitly not proxying to BD. It also distinguishes itself from the YouTube/Vimeo path the owner might otherwise supply, so an agent can tell what it does and does not cover without inspecting the schema.

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

Usage Guidelines5/5

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

The 'Use when' line gives an explicit trigger (owner wants a background video and has supplied no YouTube/Vimeo link), and the body adds the selection heuristic: pass several candidates in one call, pick a landscape clip for a wide background, prefer a smaller file. It also tells the agent how to source the URLs via a web search and what Pexels video links look like.

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