Skip to main content
Glama

cloud_project

Manage Blackmagic Cloud projects in DaVinci Resolve by loading, creating, importing from a file path, or restoring from a folder, with sync and collaboration options.

Instructions

Blackmagic Cloud projects. action: 'load', 'create', 'import' (from file path) or 'restore' (from folder path). sync_mode: CLOUD_SYNC_NONE, CLOUD_SYNC_PROXY_ONLY or CLOUD_SYNC_PROXY_AND_ORIG.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "cloud_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
actionYes
is_collabNo
sync_modeNo
media_pathNo
project_nameNo
camera_accessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is partly covered. Beyond that the description says nothing about what 'load' vs 'restore' actually changes on disk, whether restore overwrites existing project data, whether cloud credentials/network are required, or what happens to unsynced local changes.

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

Conciseness3/5

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

Very short and front-loaded, with no filler sentences. The telegraphic fragment style ('Blackmagic Cloud projects.') and missing connectors make it read like notes rather than a specification, and the terse format comes at the cost of the missing parameter and behavior detail.

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

Completeness3/5

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

Given 7 parameters at 0% schema coverage, four undocumented parameters, and no output schema, the definition is under-specified for a mutating multi-action tool. It covers the action/path axis adequately but leaves the collab, media path, project name and camera access parameters and all return behavior unexplained.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description must compensate. It usefully supplies the valid action values (the schema has no enum) and ties `path` to import/restore, but is_collab, media_path, project_name and camera_access are left completely undefined in both schema and description.

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?

Names the resource (Blackmagic Cloud projects) and enumerates the action values ('load', 'create', 'import', 'restore'), so an agent knows this is a multi-mode project operation. It does not, however, distinguish itself from overlapping siblings such as create_project, import_project or open_project, so the boundary is left implicit.

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?

The parentheticals ('import' from file `path`, 'restore' from folder `path`) hint at when each mode applies, but there is no explicit when-to-use guidance and no named alternative despite several siblings that appear to overlap. An agent must guess whether to call cloud_project action='create' or create_project.

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