Skip to main content
Glama

nudge

Move selected clips in Final Cut Pro timelines left, right, up, or down by precise frame increments for precise timeline adjustments.

Instructions

Nudge selected clip(s) in a direction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directionYesDirection to nudge
largeNoIf true, nudge by a larger amount (10 frames instead of 1)
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention if this is destructive, requires specific permissions, affects other clips, or has side effects like updating timelines, which is inadequate for a mutation tool.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded and clear in its brevity, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations or output schema, the description is incomplete for a tool that likely mutates timeline clips. It lacks details on behavior, effects, or return values, leaving significant gaps in understanding how the tool operates in context.

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 the schema fully documents parameters. The description adds no meaning beyond the schema, as it doesn't explain 'nudge' in terms of direction or large amounts. Baseline 3 is appropriate since the schema handles parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('nudge') and target ('selected clip(s)'), but it's vague about what 'nudge' means in this context—likely moving clips in a timeline, but not explicitly stated. It doesn't differentiate from siblings like 'trim' or 'move', which might have overlapping functions.

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 is provided on when to use this tool versus alternatives like 'trim', 'move', or timeline adjustments. The description lacks context about prerequisites (e.g., needing clips selected) or exclusions, leaving usage unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elliotttate/finalcutpro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server