Skip to main content
Glama

add_shot

Inserts one empty shot right after the shot on screen and returns its id. It inherits place, light and look from the previous shot so you can fill in cast, action, words, camera and transition.

Instructions

Add one empty shot (no cast, no scenery items; place, light and look carry on from the shot before, like the app's + Shot). By default it goes right after the shot on screen. Returns the new shot id. Then fill it with cast, act, words, camera, light, place and transition. One undo step for the person. For a new place or moment use add_scene; to copy a shot use duplicate.

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": "add_shot"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPut it right after this shot id.
firstNoWith scene: put it first in the scene instead.
lightNoLighting preset id (library lights).
placeNoPlace preset id, with its scenery. Ids must come from the current style: call library to see them (a wrong id is refused with the valid list).
sceneNoOr: add it at the end of this scene (id or index).
cameraNoCamera move id (library cameras).
secondsNoLength in seconds (3 if left out).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / camera / description
      Previous value: -"Camera move id."New value: +"Camera move id (library cameras)."
    • changedInput schema / properties / light / description
      Previous value: -"Lighting preset id."New value: +"Lighting preset id (library lights)."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false), the description discloses the key behaviors: the shot is created empty, place/light/look are inherited from the preceding shot, the default insertion point is right after the on-screen shot, the return value is the new shot id, and the operation collapses into one undo step.

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?

Front-loaded with the core action, then the empty-shot constraint, default placement, return value, follow-up, and alternatives — each sentence carries distinct information with no restatement of the name or schema.

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

Completeness5/5

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

For a 7-parameter, non-idempotent mutation with no output schema, the definition covers what gets created, where it lands, what it inherits, what it returns, and how to undo it — everything needed to invoke it safely and correctly.

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. The description still adds value the schema does not: it explains the default placement ('right after the shot on screen') when no after/scene/first is supplied, and clarifies the post-creation fill workflow that maps to the preset params.

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?

States a concrete verb+resource ('Add one empty shot') and immediately bounds the scope ('no cast, no scenery items'), which distinguishes it from filler tools like cast or place. It also names what it is not — add_scene and duplicate — so an agent can route correctly without opening sibling schemas.

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?

Explicitly names alternatives with the selecting condition: 'For a new place or moment use add_scene; to copy a shot use duplicate.' It also gives the follow-on workflow ('Then fill it with cast, act, words, camera, light, place and transition'), covering both when to use and what to do next.

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