Identifies empty gaps in a Premiere Pro timeline so you can locate missing clips and fill sequence holes.
Premiere Pro expanded operation: get timeline gaps.
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": "get_timeline_gaps"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden for behavioral disclosure. It does not state whether the operation is read-only, what output it returns, error conditions, or any side effects. The agent is left without essential information about this tool's runtime 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 concise (one sentence) and not verbose, which is good. However, it is under-specified and does not convey more than the name already implies. It lacks any structuring or additional context that would earn a higher score.
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?
There is no output schema, no annotations, and a minimal description. The tool might return data about timeline gaps, but nothing is stated about format, timing, or prerequisites. This is severely incomplete for an agent to use effectively.
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, so the description does not need to explain them. The schema is permissive with additionalProperties, but parameter count is 0. Baseline 4 is appropriate since no parameter documentation 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 states 'get timeline gaps' which identifies a specific resource (timeline gaps) but does not clarify what constitutes a gap or the scope. It distinguishes from siblings by naming 'gaps' but lacks detail on the actual result or context.
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?
No guidance is provided on when to use this tool versus alternatives like get_timeline_summary or get_sequence_structure. The phrase 'expanded operation' is vague and does not offer any practical usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.