Skip to main content
Glama

Video thumbnail metadata

bpj_video_thumbnail_metadata
Read-onlyIdempotent

Build VideoObject metadata with a thumbnail, upload date and duration in seconds.

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": {
      "name": "<name>",
      "thumbnail": "<thumbnail>",
      "uploaded": "<uploaded>",
      "seconds": "<seconds>"
    },
    "name": "bpj_video_thumbnail_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
secondsYes
uploadedYes
thumbnailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds the meaningful behavioral detail that the output is schema.org VideoObject metadata rather than raw inputs, but it never says what form that takes (JSON-LD string vs. object), whether inputs are validated, or how invalid values are handled.

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, and the key resource type appears immediately. It is efficiently written, though the terseness is part of why other dimensions are thin.

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?

Four required parameters, no output schema, and none of the parameter formats documented means the description should do more than it does. An agent still cannot tell what the call returns or what string formats 'uploaded' and 'thumbnail' require, which matters for a metadata-construction tool.

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%, so the description must carry parameter meaning, and it only names three of the four inputs (thumbnail, upload date, duration in seconds) while omitting 'name'. It adds no format guidance for the ambiguous 'uploaded' string (ISO 8601? date only?) and does not explain the constraints baked into the schema, such as the 604800-second (7-day) duration ceiling or the 240-character limits.

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 uses a specific verb ('Build') with a named resource ('VideoObject metadata') and lists the fields it packages, which distinguishes it from sibling bpj_*_metadata builders that target other schema types. It doesn't explicitly contrast with those siblings, but the schema.org type name is enough for an agent to tell it apart.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g., needing an existing video page or thumbnail asset), and no reference to alternatives among the many sibling metadata builders. Usage is only implied by the resource name.

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.