Skip to main content
Glama
Sign In
Bannerbear MCP Server

Bannerbear MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create video slideshow

create_video_slideshow
Destructive

Generate a video slideshow from multiple image URLs with configurable transitions, slide duration, dimensions, and optional metadata.

Instructions

POST /v5/tools/create_video_slideshow. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Mandatory confirmation before provider execution; one submission only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_video_slideshow"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoExact private workspace profile label; no fallback to another profile key.
confirmNoMust be true for this exact requested render, upload, edit, install or delete.
payloadNoComplete current native JSON body. Use payload or payload_file exclusively.
payload_fileNoRegular non-symlink local JSON file, at most 1 MiB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description goes beyond them usefully by disclosing credit consumption ("credits apply"), provider scope/lock behavior, a required confirmation step, and non-retryability ("one submission only") — real operational constraints an agent needs.

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?

Two tightly packed sentences with no filler, and the endpoint/operation identity is front-loaded. It is arguably under-specified rather than verbose, but nothing is wasted.

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?

For a destructive, non-idempotent, open-world operation with no output schema, the description covers confirmation, credits, and single-submission semantics. However it never says what the slideshow render produces or how completion is observed, leaving a minimum-viable gap given the tool's complexity.

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%, so every parameter (account, confirm, payload, payload_file) already carries documentation, including the nested payload fields and the "Use payload or payload_file exclusively" rule. The description adds nothing param-specific, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description essentially restates the tool name and its HTTP route ("POST /v5/tools/create_video_slideshow... Current Bannerbear V5 operation") without explaining what a slideshow is built from. It offers no differentiation from video siblings like generate_ai_video, concat_videos, or create_animation, which an agent must choose between.

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 only usage directive is "Mandatory confirmation before provider execution," which is a precondition rather than a when-to-use rule. There is no guidance on when to pick this over concat_videos, generate_ai_video, or create_animation, so sibling selection is left entirely to inference.

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