Skip to main content
Glama

list_projects

Read-only

Lists projects and subfolders in the current or specified DaVinci Resolve project-manager folder, with optional attributes like dates, notes, and collaboration mode.

Instructions

Projects and sub-folders in the current project-manager folder, or in folder (a path from the root, "/" = root; navigating changes the current folder). Optionally with attributes (created / modified dates, notes, collaboration mode).

Tool call template

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": "list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNo
with_attributesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior beyond that: navigating via the folder path changes the tool's current folder state, and with_attributes expands the payload with dates, notes, and collaboration mode.

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?

Two sentences, front-loaded with the resource being listed, with parameter meaning packed into parentheticals. The stacked parentheses make it slightly dense, but no sentence is wasted and nothing essential is buried.

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?

For a two-optional-parameter read-only listing tool with no output schema and annotations covering safety, the description supplies the missing parameter meaning and the folder-state side effect. It could say more about ordering or result limits, but that is a minor gap at this complexity.

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?

Schema description coverage is 0%, so the description carries the full burden and does so well: `folder` is explained as a root-relative path where "/" is root and navigation mutates current context, and `with_attributes` is explained as adding dates, notes, and collaboration mode. Only the null/default-folder behavior is left implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: projects and sub-folders in the current project-manager folder or a named folder. An agent can tell this is a directory-listing tool for the project manager, though it does not explicitly contrast itself with sibling list_* tools.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the folder parameter and the note that navigating changes the current folder, which hints at a browse-then-descend workflow. There is no explicit when-to-use statement, no exclusions, and no named alternative for listing projects by other criteria.

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

Deploy Server

Other Tools