Clicks a Final Cut Pro menu item by path, such as Modify > Balance Color, or lists that menu's items when given one menu name. Use it to trigger FCP commands from Claude Code.
Click a Final Cut Pro menu item, e.g. ["Modify", "Balance Color"] or ["File", "Share", "Master File (default)…"]. With a single entry (["Modify"]) it lists that menu's items instead of clicking.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully discloses the dual behavior of clicking a menu path versus listing items when one entry is supplied, but it does not mention preconditions such as Final Cut Pro being open/frontmost, side effects of clicking arbitrary menu items, or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loads the core action, and uses examples efficiently. Every sentence adds useful information about how the path argument behaves.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, no-output-schema tool, the description covers the essential invocation semantics and the listing mode well. However, because there are no annotations and no output schema, it should ideally also state basic preconditions and clarify what is returned in the listing mode or after a click.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate for the bare array-typed path parameter. It does so well: the examples show ordered menu traversal, including nested submenus like ["File", "Share", "Master File (default)…"], and it explains the special single-element semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: "Click a Final Cut Pro menu item," and the examples make the intended operation concrete. It also explains that a single-entry path lists menu items instead of clicking, which clarifies the tool's dual behavior, though it does not explicitly distinguish this from sibling tools such as fcp_shortcut.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear usage context for the single-entry case: "With a single entry (["Modify"]) it lists that menu's items instead of clicking." However, it does not say when to choose this tool rather than alternatives like fcp_shortcut or fcp_go_to, so usage guidance is mostly implied by the examples.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.