Skip to main content
Glama

Apply visual presets

visuals_apply
DestructiveIdempotent

Create or update up to 20 visual blocks in one call after edit timing is settled. Presets: broll-headline, steps, quote, end-screen, key-number, before-after, screenshot-focus, chapter. IDs are scoped to the project; repeating an ID updates it. Asset IDs must belong to the workspace. Atomic, undoable; dryRun validates without writing. Returns IDs and revision. No generation pass.

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>",
      "items": "<items>",
      "expectedRevision": "<expectedRevision>",
      "dryRun": "<dryRun>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "visuals_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesSupply only the fields for the selected preset.
dryRunYes
projectIdYesUUID string.
idempotencyKeyYes
expectedRevisionYes

Output Schema

NameRequiredDescriptionDefault
itemsYes
dryRunYes
successYes
replayedYes
revisionYes
warningsYes
mutationReceiptIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / accentColor
      Added value: +{
      +  "description": "Brand accent for key-number or screenshot-focus.",
      +  "pattern": "^#[0-9a-fA-F]{6}$",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare destructive/idempotent/not-read-only; the description adds substantial context beyond them: atomicity, undoability, dryRun semantics, workspace scoping of asset IDs, project-scoped IDs, and that repeating an ID performs an update. The update-on-repeat behavior is consistent with idempotentHint=true and the mutation verbs are consistent with destructiveHint=true, so nothing is contradicted.

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?

Front-loads the operation and scope, then moves through presets, ID semantics, asset constraints, atomicity/dryRun, and return values in a tight sequence of fragments. Nearly every clause carries an actionable constraint; nothing is repeated from title or annotations.

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?

Return values need not be described because an output schema exists, yet the two hardest required parameters for a destructive batch write — expectedRevision and idempotencyKey — are left unexplained, which is exactly where an agent is most likely to mis-call. For a 20-item destructive mutation, completeness is adequate but has a meaningful hole.

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 40% and the description compensates for some of that: project-scoped IDs, asset IDs must belong to the workspace, and per-preset field supply. But it says nothing about expectedRevision (a required concurrency token) or idempotencyKey, and the preset list it enumerates is already in the schema enum, so key parameters remain undefined in prose.

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?

States a specific verb and resource ('Create or update ... visual blocks'), the batch ceiling (20), and that it happens in one call. The closing 'No generation pass' explicitly separates it from generative siblings, so an agent can tell what this tool is and is not without opening the schema.

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?

Gives a real precondition ('after edit timing is settled') that tells the agent when the call is safe, plus a dryRun path for validation-only calls. It does not name a concrete alternative sibling for the non-settled case, so it stops short of full when/when-not 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.

Resources