Skip to main content
Glama

filmcraft_inspect_project

Inspect the active FilmCraft or Premiere Pro project to retrieve its name, bins, media clips, durations, and active sequence for accurate editing decisions.

Instructions

Inspects the active FilmCraft or Premiere Pro project, returning the project name, bins, imported media clips, durations, and active sequence.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the definition carries the full behavioral burden. 'Inspects' implies a read-only, non-mutating call, and the field list gives a good sense of what comes back, but nothing states that no state is changed, what happens if no project is open or no host is targeted, or whether this is expensive/slow.

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?

A single sentence with the resource front-loaded and the payload enumerated immediately after — no filler, no restatement of the title.

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?

Because there is no output schema, the description must name the return values, and it does so comprehensively (project name, bins, clips, durations, active sequence). The remaining gap is failure/edge-case behavior (no active project, host not connected), which matters for a host-dependent inspection tool.

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?

The tool takes zero parameters, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly adds no parameter noise.

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?

The definition pairs the specific verb 'inspects' with a concrete resource ('the active FilmCraft or Premiere Pro project') and enumerates the returned fields (name, bins, clips, durations, active sequence). This clearly separates it from filmcraft_inspect_timeline, though that sibling is never named as such, so differentiation has to be inferred.

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 only implied: 'inspects the active ... project' suggests calling it to discover project state before acting on bins/clips/sequences. There is no explicit when-to-use guidance, no statement of preconditions (e.g., a connected host via vibie_set_target_host), and no exclusions relative to inspect_timeline.

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