Skip to main content
Glama

Make a postable video from your upload

use_own_video

Turns a ready 'own' upload into a video you can post: whole, or trimmed to start/end seconds. A short content check runs first either way: poll get_video until status ready.

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": {
      "source_id": "<source_id>"
    },
    "name": "use_own_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
source_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent operation. The description adds real value by disclosing the content check that runs on every call and the required prerequisite polling, but it leaves open what happens if the check fails, whether a failed call is retryable, or whether quota is consumed.

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?

Two sentences with the primary outcome front-loaded, followed by the operational gate. No filler or restatement of the tool name.

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 3-parameter mutation with no output schema and zero schema descriptions, the definition covers purpose and the readiness prerequisite but omits what is returned (new video id? status?) and any limits on trimming range. Adequate to invoke, incomplete to invoke confidently.

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 0%, so the description carries the burden. It clarifies that start/end are second offsets used for trimming and that source_id refers to a ready 'own' upload, but says nothing about end exclusivity, whether start/end can be supplied independently, or the expected source_id shape.

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?

States a concrete verb and resource: turning a ready 'own' upload into a postable video, with two modes (whole or trimmed). The transform is distinct from siblings like stitch_videos, though the description never names an alternative to route between them.

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

Usage Guidelines4/5

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

Gives a clear precondition gate: the upload must be ready, verified by polling get_video until status ready. It does not set exclusions or point to alternatives, so the agent knows when it may call this but not when it should prefer something else.

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.