aviutl2-mcp

Overview Schema Source Related Servers Discussions Admin

オブジェクトの編集

update_object

Modify an existing object's layer, frame range, and effect parameters using its index. Merge updates into specific effects or add/remove filters for fine-grained control.

Instructions

既存オブジェクトのレイヤー/フレーム範囲/エフェクトパラメータを変更する。object_index は read_project が返す index。effect_index を指定してそのエフェクトの params をマージ更新する。

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": {
      "path": "<path>",
      "object_index": "<object_index>"
    },
    "name": "update_object"
  }
}

Input Schema

Name	Required	Description
`path`	Yes
`layer`	No
`scene`	No
`params`	No	effect_index のエフェクトにマージするパラメータ
`frame_end`	No
`add_filters`	No	描画エフェクトの直前に追加するフィルタ効果
`frame_start`	No
`effect_index`	No	パラメータを変更するエフェクトの番号 (0=メディア入力)
`object_index`	Yes
`remove_effect_index`	No	削除するエフェクト番号 (先頭と末尾は削除不可)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, but it only discloses the merge-update behavior for params and the source of object_index. It does not mention side effects, reversibility, permissions, or error conditions, which are particularly relevant for a mutation tool. The merge behavior is already partially stated in the schema, so the description adds limited extra transparency.

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 compact at two sentences, front-loads the primary action, and adds only essential clarifications about object_index and effect_index. Every phrase is useful, and it neither repeats schema information nor wastes words.

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?

For a complex tool with 10 parameters, no annotations, and no output schema, the description is too terse. It covers the core action but omits critical context such as return values, behavior for edge cases (e.g., invalid indexes, deletion restrictions), and relationships with related tools. The description does not give an agent enough to safely invoke the tool in all scenarios.

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 only 40%, so the description should compensate, but it only directly explains object_index (from read_project) and effect_index ('specify to merge-update its params'). It hints at layer/frame range via 'レイヤー/フレーム範囲' but does not detail the individual parameters like layer, frame_start, frame_end, or path. The merge behavior is also already in the schema, so added value is moderate.

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

Purpose5/5

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

The description clearly states the verb (変更する, to modify) and the resource (既存オブジェクト, existing object), and lists the specific aspects being modified (layer/frame range/effect parameters). It distinguishes the tool from siblings like delete_object and add_objects by focusing on editing an existing object.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: it is for modifying existing objects, implying it should be used after reading a project (object_index from read_project). However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of a full 5.

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