Skip to main content
Glama

film.update_look

Set the project's film look (§36). Fields merge into the current look unless replace is true. Set this first: every shot prompt inherits it.

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": {
      "projectId": "<projectId>",
      "expectedVersion": "<expectedVersion>",
      "look": "<look>"
    },
    "name": "film.update_look"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookYesProject-wide look applied to every shot prompt. An empty string clears a field.
replaceNo
projectIdYes
expectedVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two non-obvious traits: fields merge by default and downstream shot prompts inherit the look. However, it is silent on concurrency behavior for expectedVersion, permissions, and reversibility of an overwrite, which matter for a mutation tool.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action, then the mutation semantics, then the ordering constraint. No filler and nothing buried.

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?

For a tool whose nested `look` object has ten fields with only aspectRatio documented and a required expectedVersion with no stated meaning, the description does not fill the gap. It covers inheritance and merge behavior well but leaves the hard parts of the call under-explained.

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

Parameters3/5

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

Schema description coverage is 25%, and the description usefully explains the merge-vs-replace semantics of the `replace` flag, which the schema leaves bare. It adds nothing for projectId or expectedVersion, so the optimistic-concurrency parameter remains opaque in both places.

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?

States a specific verb and resource ("Set the project's film look") and scopes it to the project, which cleanly separates it from film.get_look among the siblings. It stops short of explicitly naming the read counterpart, but the write/read split is unambiguous.

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

Usage Guidelines4/5

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

"Set this first: every shot prompt inherits it" gives clear ordering and dependency guidance that an agent can act on. It does not explicitly state when-not-to-use or point at film.get_look for reading, so it falls short of full alternative-routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.