Vibie MCP

vibie_set_target_host

Switches which video editor receives edits, letting you route changes to FilmCraft, Adobe Premiere Pro, or auto-detect the open app.

Instructions

Switches which video editor receives edits (FilmCraft or Adobe Premiere Pro).

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": {
      "target": "<target>"
    },
    "name": "vibie_set_target_host"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes	Target NLE: 'filmcraft', 'premiere', or 'auto' (whichever is open)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 29, 2026

TDQS

B3.4/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 discloses that this redirects edit routing to one of two editors, but says nothing about whether the change persists across calls, what happens if the chosen host isn't running, or what errors look like.

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 front-loaded sentence with zero filler. It is efficient, though the terseness leaves the remaining gaps unfilled.

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 one-parameter routing switch with full schema coverage and no output schema, the core is covered. Still missing is the relationship to vibie_detect_hosts and the failure/persistence behavior of the switch.

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% and the enum field already explains 'auto' as 'whichever is open'. The description only restates the two editor names, adding no format or behavioral detail beyond the schema.

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: 'Switches which video editor receives edits', naming both possible editors. It is distinguishable from vibie_detect_hosts (detection vs. configuration), though it never explicitly contrasts with that sibling.

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 — an agent can infer this should be called before issuing edits, but the description never says when to set a target versus calling vibie_detect_hosts, or when 'auto' is preferred.

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