Sets an XMP metadata property on a Premiere Pro project item by node ID, letting you update clip details such as description or label.
Set a metadata (XMP) property on a project item
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | Value to set | |
| nodeId | Yes | The nodeId of the project item | |
| property | Yes | XMP property name/path (e.g. 'dc:description', 'xmp:Label') |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It identifies an XMP mutation on a project item, but does not disclose overwrite behavior, required XMP namespaces, permissions, or failure semantics.
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 a single front-loaded sentence with no wasted words. It is appropriately sized for a simple three-parameter setter.
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?
The schema fully documents the three required parameters, which keeps the description minimally viable. However, with no annotations and no output schema, the definition should say more about mutation behavior and sibling alternatives.
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 description coverage is 100%, so the schema already documents nodeId, property, and value. The description adds only high-level context that the property is an XMP metadata field on a project item, not additional parameter syntax or constraints.
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: set an XMP metadata property on a project item. It is clear what the tool does, but it does not distinguish itself from related siblings such as set_xmp_metadata or set_clip_description.
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?
There is no guidance on when to use this tool instead of set_xmp_metadata, get_xmp_metadata, or set_clip_description. An agent must infer the choice from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.