Set selected clips to offline in Adobe Premiere Pro to detach them from source media and manage relinking.
Premiere Pro expanded operation: set offline.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "set_offline"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full responsibility for disclosing behavior, but it discloses nothing beyond restating the tool name. It does not state whether the operation affects selected clips, project items, media files, or whether it is reversible or requires specific conditions.
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 short, but brevity here is under-specification rather than conciseness. The single sentence does not earn its place because it provides no useful information beyond the tool name, while lacking structure to convey any actionable guidance.
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 tool operating in a complex domain like Premiere Pro media offline management, the description is completely inadequate. It has no annotations, no output schema, and no explanation of the operation's scope, effects, or relationship to other tools, leaving the agent without essential context.
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?
The tool has zero parameters and the input schema is empty, so the parameter semantics burden is minimal. Per the rubric, 0 params receives a baseline of 4, and no additional parameter explanation is needed.
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 is essentially a tautology: "set offline" restates the tool name without saying what resource or state is affected. It does not distinguish this from siblings like check_offline_media, get_offline_media, or relink_media, and the generic "Premiere Pro expanded operation" prefix adds no specific meaning.
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 versus alternatives. It does not mention prerequisites, typical workflows, or how it relates to offline media handling in Premiere Pro. A user or agent cannot determine the appropriate context from the description alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.