Skip to main content
Glama

get_edit

Get detailed information about a specific edit, optionally including scenes and shots.

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_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
editIdYesThe edit ID
workspaceIdYesThe workspace ID
includeShotsNoInclude shot data
includeScenesNoInclude scene data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read ('Get') but says nothing about permissions, response size, whether requesting shots/scenes is expensive, or how this differs in payload from get_edit_full.

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 efficient sentence with the resource front-loaded and the optional behavior appended. No filler, though it is arguably too terse for a tool with a near-identical sibling.

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 read tool with full schema coverage and no output schema, the description is minimally adequate. The significant omission is disambiguation from get_edit_full, which an agent in this 130-tool namespace genuinely needs.

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 100%, so all four parameters are already documented in the schema. The description's 'optionally including scenes and shots' merely restates includeScenes/includeShots without adding format or cost semantics, so the baseline 3 applies.

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 specific verb and resource ('Get detailed information about a specific edit') and even flags the optional expansion of scenes/shots. However, it does not differentiate itself from the obviously related sibling get_edit_full, leaving the agent unsure which 'get' to pick.

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?

No guidance on when to use this versus get_edit_full, list_edits, or inspect_edit_frame. The word 'optionally' hints at the include flags but the description never states the condition under which scenes/shots should be requested.

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.