Skip to main content
Glama

get_shot

Get a shot by its ID or its one-based number in the edit, in scene then shot order. Returns the selected start frame and settings for a shot image retake.

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": {
      "workspaceId": "<workspaceId>",
      "editId": "<editId>"
    },
    "name": "get_shot"
  }
}

Input Schema

NameRequiredDescriptionDefault
editIdYesThe edit ID
shotIdNoThe shot ID. Provide either shotId or shotNumber.
shotNumberNoOne-based position in the ordered edit. Use when the user gives a shot number.
workspaceIdYesThe workspace ID
includeLinkedMediaNoSet false for a compact shot and selected image settings without full media records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / includeLinkedMedia
      Added value: +{
      +  "default": true,
      +  "description": "Set false for a compact shot and selected image settings without full media records.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / shotId / description
      Previous value: -"The shot ID"New value: +"The shot ID. Provide either shotId or shotNumber."
    • addedInput schema / properties / shotNumber
      Added value: +{
      +  "description": "One-based position in the ordered edit. Use when the user gives a shot number.",
      +  "exclusiveMinimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "workspaceId",
      -  "editId",
      -  "shotId"
      -]New value: +[
      +  "workspaceId",
      +  "editId"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the payload contents ("selected start frame and settings for a shot image retake"), which is genuinely useful given there is no output schema, but it never states that this is a non-mutating read, what error occurs for an unknown shot ID, or how includeLinkedMedia changes the shape beyond what the schema already says.

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 short sentences, lookup keys and ordering front-loaded, and the return payload summarized second. No filler, no restatement of the tool name.

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 a low-complexity getter with no annotations and no output schema, the description covers purpose, both lookup modes, and the essential return contents. The only meaningful omissions are the precedence rule when both shotId and shotNumber are supplied and the effect of includeLinkedMedia, both of which remain inferable only from the schema.

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 coverage is 100%, with every parameter already documented, so the baseline is 3. The description adds a little meaning beyond the schema by clarifying that shot ordering is scene then shot order and that shotNumber is one-based within that ordering, but it says nothing about shotId/shotNumber precedence or the includeLinkedMedia compact mode.

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?

"Get a shot" states a specific verb and resource, and the description goes further by naming both lookup keys (shot ID or one-based number in the edit) and the ordering rule (scene then shot order). That level of detail makes it distinguishable from read siblings like get_edit or get_media, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the reader can infer that shotNumber is the right key when a user speaks in ordinal terms, and the mention of "settings for a shot image retake" hints at the retake workflow. There is no explicit when-to-use/when-not guidance and no named alternative such as get_edit for edit-level data, leaving routing to inference.

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.