Skip to main content
Glama

manage_album

Create still or PowerGrade albums, rename existing albums, or set an album as current in DaVinci Resolve.

Instructions

Create a still or PowerGrade album, rename an album, or make it the current album.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
albumNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 the safety profile is known. The description adds only that one operation makes an album 'current', i.e. a state mutation, but says nothing about whether rename overwrites an existing name, whether a failed action is recoverable, what permissions are needed, or what happens when the named album does not exist.

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?

A single front-loaded sentence that lists the operations without filler. It is efficient, though the comma-separated operation list could have been structured to pair each action with its parameters.

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

Completeness2/5

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

This is a mutation tool with three parameters at 0% schema coverage and no output schema. The description does not compensate: it omits the name/album parameter mapping, per-action requirements, and error behavior, leaving the agent to guess how to invoke each of the four actions correctly.

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%, so the description must carry parameter meaning, and it does not. The two similarly-named parameters 'name' and 'album' are never disambiguated (presumably target album vs. new name for rename), and the description never states which parameter each action requires or ignores.

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 names a specific verb set and resource (create a still/PowerGrade album, rename, set current) and maps cleanly onto the four enum values of the action parameter. It is clear what the tool does, though it does not distinguish itself from sibling tools like manage_stills or manage_color_group.

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 by the enumerated operations, so an agent can infer that 'rename' or 'set_current' is the path for those tasks. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to an alternative tool for overlapping album/still operations.

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