close_all_source_clips
Closes every clip in the Source Monitor simultaneously, freeing the panel for new media.
Instructions
Close all clips in the Source Monitor.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Closes every clip in the Source Monitor simultaneously, freeing the panel for new media.
Close all clips in the Source Monitor.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description confirms the destructive nature (close all clips) which aligns with annotations (destructiveHint: true). However, it does not add new behavioral context beyond what annotations already provide.
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?
Single highly concise sentence front-loads the action and resource. No wasted words.
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 simple tool with no parameters and no output schema, the description fully captures the action and scope. No missing details.
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?
No parameters present, so schema coverage is 100% and description does not need to elaborate. Baseline of 4 is appropriate for zero-parameter tools.
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?
Clearly states the specific verb 'Close' and resource 'all clips in the Source Monitor'. Differentiates from sibling tool close_source_monitor which closes the monitor itself.
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 on when to use this tool versus alternatives like close_source_monitor or other clip management tools. The description only states what it does, not when to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/leancoderkavy/premiere-pro-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server