Skip to main content
Glama

setEditorSettings

Change an OpenScreen project's look—frame, wallpaper, webcam, cursor, audio—by passing only the settings to change.

Instructions

Change the project's look: pass only the settings to change, named as getCurrentDocument returns them under settings. Background: wallpaper (a bundled path from settingsContext.bundledWallpapers, a CSS colour or gradient, or a base64 PNG/JPEG data URL; never a file path or web URL; an embedded image reads back as a marker, leave the key out to keep it), wallpaperMotion (moves a gradient or image only), backgroundBlur 0–1. Frame: aspectRatio ("auto", a preset, or an originalAspectRatios token; a fixed format picked for the first time fills the frame with a window that follows the cursor, which formatFollowCursor turns off when settingsContext.formatFill is "available"), padding 0–100 %, borderRadius 0–64 px, shadowIntensity 0–1, frame (none, window, laptop, phone, monitor) and frameTheme (light, dark), motionBlurAmount 0–1, depthOfField (blurs 3D-tilted zooms only). Camera: webcamLayoutPreset, webcamMirrored, webcamReactiveZoom (shrinks on zoom), webcamMaskShape (square or rectangle, the camera's own proportions; an untouched roundness follows it), webcamRoundness 0–1, webcamSizePreset 15–60, webcamAnchor (a corner or an edge middle), webcamCropRegion (the framing: a square share of the picture, width = height ≥ 1/3) and webcamCropPan (where that window sits, 0–1 per axis, 0.5 centred), webcamBackgroundMode (none, transparent, blur, custom: needs settingsContext.cameraSegmentation ready), webcamBlurIntensity 0–1, webcamWallpaper (as wallpaper). Cursor, under cursor: show, autoHide, theme (settingsContext.cursorThemes), asArrow (the recorded cursor kinds drawn as the arrow instead), size 1.5–6, smoothing 0–1, motionBlur 0–1, clickBounce 0–2, clickImpact, clickSound (only heard when the take recorded clicks) and clickSoundGainDb −24–0, model3d. Also autoFocusAll (every zoom follows the cursor) and audioGainDb −12–12 dB, the master volume. A value out of range or a key not listed is refused with the reason, and nothing changes. The result lists what was applied, including what the editor changes with it, and inactive for any of those the current state leaves without effect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameNo
cursorNo
paddingNoPercent.
projectIdNoThe project to act on, from listProjects. Omit it only for the project open in the OpenScreen editor, which works only while the app runs.
wallpaperNoA bundled wallpaper path (settingsContext.bundledWallpapers), a CSS colour (#1e1e2e, rgb(…)), a CSS gradient, or a base64 PNG/JPEG data URL. No file paths, no web URLs.
frameThemeNo
aspectRatioNo"auto", one of the presets, or a token from settingsContext.originalAspectRatios.
audioGainDbNo
autoFocusAllNo
borderRadiusNoCorner radius in px at 1080p.
depthOfFieldNo
webcamAnchorNo
webcamCropPanNo
backgroundBlurNo
webcamMirroredNo
shadowIntensityNo
wallpaperMotionNo
webcamMaskShapeNo
webcamRoundnessNo
webcamWallpaperNo
motionBlurAmountNo
webcamCropRegionNo
webcamSizePresetNoThe camera's long side, in percent of the frame's short side.
formatFollowCursorNo
webcamLayoutPresetNo
webcamReactiveZoomNo
webcamBlurIntensityNo
webcamBackgroundModeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4/5.0
Behavior5/5

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

Annotations only carry the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds substantial behaviour beyond that: rejection of out-of-range values or unknown keys with nothing changed (atomicity), a return value listing what was applied plus an `inactive` set for settings without effect, and cross-field interactions like formatFollowCursor overriding the fill-follows-cursor behaviour.

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?

The instruction and merge rule are front-loaded in the first sentence, and the category labels (Background:/Frame:/Camera:) give scannable structure. It is still a single dense paragraph for 28 keys, and some range-only entries such as "motionBlurAmount 0–1" add little, but the bulk of the length is justified by the parameter surface.

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 28-parameter mutation tool with no output schema, the description covers the merge contract, validation failure behaviour, the shape of the result including `inactive`, and a dependency precondition. It is close to complete; only the few unexplained keys and the absence of any undo/reversibility note leave a gap.

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 only 21%, so the description must compensate, and it largely does: it enumerates nearly all 28 keys grouped by Background/Frame/Camera/Cursor and adds meaning the schema lacks (wallpaper accepted formats, per-axis cropPan with 0.5 = centred, cropRegion width = height ≥ 1/3, aspectRatio token sourcing). A handful of keys (frameTheme, webcamLayoutPreset, webcamMirrored, shadowIntensity) are named with no added semantics, keeping it short of a 5.

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?

"Change the project's look: pass only the settings to change, named as getCurrentDocument returns them under `settings`" is a specific verb+resource with clear merge semantics, and it points at the sibling that supplies the shape. It does not, however, disambiguate against siblings that also touch these fields (setAspectRatio, setProjectInfo, setEffect), so a 5 is withheld.

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?

The description implies when to use it — only pass the keys you want changed, and read current values from getCurrentDocument — and it discloses preconditions such as settingsContext.cameraSegmentation being required for webcamBackgroundMode "custom". But there is no explicit when-not guidance or routing versus setAspectRatio/setProjectInfo, which overlap on individual fields.

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