Skip to main content
Glama
hoyt-harness

DaVinci MCP Professional

by hoyt-harness
OverviewSchemaRelated ServersScoreDiscussions
Python

list_media_clips

Retrieve a complete list of all clips in the DaVinci Resolve media pool to quickly locate and organize your video assets for editing.

Instructions

List all clips in the media pool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/davinci_mcp/tools/__init__.py:127-131 (registration)
    Tool schema registration: defines 'list_media_clips' with no input parameters and description 'List all clips in the media pool'.
    types.Tool(
    name="list_media_clips",
    description="List all clips in the media pool",
    inputSchema={"type": "object", "properties": {}, "required": []},
),

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

The description only states 'list all clips' with no additional behavioral details such as side effects, permissions, or scope (e.g., current project vs global). For a simple list, it is minimally sufficient but lacks transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with a single sentence. It is appropriately sized but could benefit from front-loading key context like the scope of the media pool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no parameters, no output schema), the description is fairly complete for listing clips. However, it does not explain what the 'media pool' refers to, which might be ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so the description does not need to add parameter meaning. The baseline is 4 as per guidelines for zero parameters.

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 'list' and resource 'clips in the media pool', distinguishing it from sibling tools like list_projects and list_timelines.

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

Usage Guidelines2/5

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, nor any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hoyt-harness/davinci-mcp-professional'

If you have feedback or need assistance with the MCP directory API, please join our Discord server