Skip to main content
Glama

upload

Copy a local image, video, or audio file into a Dinoctor project as media, character, object, background, video, sound, music, or voice.

Instructions

Bring a file from this computer into the project, like the app's upload. Pictures (PNG/JPG/WebP/GIF/SVG): as media, character or object (joins a shot's cast or replaces a member's picture), or background. Videos (MP4/MOV/WebM): as media, video-background or video-front in a shot. Sounds (MP3/WAV/M4A...): as sound (sound Media, and on the timeline at at if given), music, or voice. Default: media for pictures and videos, sound for sounds. The file is copied into Dinoctor; the original isn't changed. One undo step. For pictures made before with Higgsfield, use put_picture.

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": {
      "path": "<path>"
    },
    "name": "upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoHow it goes into the project (see the description).
atNoFor as: sound, seconds into the film to place it on a free sound line.
nameNoA short name for it in the project.
pathYesFull path of the file on this computer.
shotNoShot id (from get_project). Default: the shot on screen.
trimNoFor a character/object picture: cut its empty see-through edges (default true).
replaceNoA cast member id in that shot whose picture this replaces.
sound_kindNoFor as: sound, what it is (guessed from the name and length otherwise).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / as / description
      Added value: +"How it goes into the project (see the description)."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the bar is lower. The description still adds real context beyond them: the file is copied rather than referenced, the source is untouched, and the action is a single undo step, which tells the agent the operation is reversible. It does not cover failure modes (missing path, unsupported codec) or what the call yields.

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?

Dense but well ordered: the core action and analogy come first, then per-file-type routing, then defaults, then the copying/undo behavior, then the sibling pointer. Every sentence carries information, though the enumerated parentheticals make it longer than strictly necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no output schema, the description covers file types, role mapping, defaults, source-file safety, and undo depth. The one remaining gap is that it never hints at what the call returns or how the created item is identified, which the absent output schema leaves to be inferred.

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%, so the baseline is 3, but the description earns more by explaining the intent of the `as` enum values beyond their labels (character/object join a shot's cast or replace a member's picture; `at` places sound on the timeline) and by stating the defaults. It leaves `trim`, `replace`, and `sound_kind` largely to their schema text, which is consistent with full schema coverage.

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 description names a specific verb and resource ('Bring a file from this computer into the project') and then enumerates exactly which file categories map to which project roles. It explicitly distinguishes itself from put_picture for previously-Higgsfield-generated pictures, so an agent can separate this from its sibling without opening either 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?

It gives concrete routing rules: pictures go to media/character/object/background, videos to media/video-background/video-front, sounds to sound/music/voice, plus a stated default ('media for pictures and videos, sound for sounds'). It also names the one explicit alternative, put_picture, and the condition that selects it.

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