Skip to main content
Glama

end_card

Adds a faded end card with custom text or logo to a video, so you can prompt followers or show branding.

Instructions

A card at the END ("Follow for more", your logo...), faded in after the video.

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": {
      "video": "<video>"
    },
    "name": "end_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoFollow for more
imageNo
videoYes
secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is partly covered. The description adds useful behavior—the card appears at the end and fades in after the video—but it does not explain whether the source video is modified in place or a new output is produced, nor does it describe duration or rendering behavior.

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?

The definition is a single compact sentence with the key placement constraint front-loaded and concrete examples in parentheses. It is efficient, though the lack of an explicit action verb slightly reduces immediate clarity.

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?

For a mutation tool with no output schema and 0% schema description coverage across four parameters, the description is too thin. It establishes the visible outcome but leaves important operational details—duration, output behavior, and parameter formats—unstated.

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

Parameters2/5

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

Schema description coverage is 0% with four parameters, so the description must carry the explanatory burden. It gives examples for text and image and implies the video parameter, but it never explains the seconds parameter or provides format guidance for image and text values.

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?

The description identifies a specific resource—a card placed at the END of a video, with examples like "Follow for more" and a logo, faded in after the video. That makes its role reasonably distinct from siblings such as title_card, though it still uses a noun phrase rather than an explicit verb like "add" or "append."

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 context provided is "after the video," which implies an end-card placement but does not explicitly say when to choose this over title_card, add_text, or add_logo. There are no exclusions, prerequisites, or alternative-tool routing.

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