Skip to main content
Glama

set_canvas_resolution

Configure the base and output resolution for OBS Studio to adjust canvas dimensions and frame rate globally across all scenes in the current collection.

Instructions

Set the OBS canvas (base) and output resolution. Applies globally — affects all scenes in the current collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYesCanvas width in pixels (e.g. 2560, 1080).
heightYesCanvas height in pixels (e.g. 1440, 1920).
fpsNoFrame rate. Defaults to 60.

Implementation Reference

  • The handler implementation for the 'set_canvas_resolution' tool, which uses `obs.call("SetVideoSettings", ...)` to update OBS base and output resolution.
    case "set_canvas_resolution": {
      const fps = args.fps ?? 60;
      await obs.call("SetVideoSettings", {
        baseWidth: args.width,
        baseHeight: args.height,
        outputWidth: args.width,
        outputHeight: args.height,
        fpsNumerator: fps,
        fpsDenominator: 1,
      });
      return ok({ canvas: `${args.width}x${args.height}`, fps });
    }
  • The tool definition (schema) for 'set_canvas_resolution' within the TOOLS array.
    {
      name: "set_canvas_resolution",
      description:
        "Set the OBS canvas (base) and output resolution. Applies globally — affects all scenes in the current collection.",
      inputSchema: {
        type: "object",
        properties: {
          width: { type: "number", description: "Canvas width in pixels (e.g. 2560, 1080)." },
          height: { type: "number", description: "Canvas height in pixels (e.g. 1440, 1920)." },
          fps: { type: "number", description: "Frame rate. Defaults to 60." },
        },
        required: ["width", "height"],
      },
    },
Behavior3/5

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

With no annotations, the description carries full burden. It discloses scope impact ('affects all scenes') but omits critical mutation details like effects on active streams/recordings, validation rules, or whether changes are immediate.

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?

Two tightly written sentences with zero waste. Critical information (global scope) is front-loaded in the second sentence. No repetition of schema details.

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?

Adequate for a 3-parameter configuration tool with complete schema coverage, but gaps remain given no output schema and no annotations. Missing safety warnings appropriate for a global state mutation (e.g., streaming interruption risks).

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 has 100% coverage with clear descriptions. The description adds minimal semantic value beyond the schema, merely grouping width/height as 'canvas' and 'output resolution' without adding format constraints or example usage patterns.

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?

Clear verb 'Set' and specific resources 'OBS canvas (base) and output resolution'. The phrase 'Applies globally — affects all scenes' effectively distinguishes this from scene-specific siblings like set_scene or set_source_visibility.

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?

Provides implicit usage context via 'Applies globally' which signals when to use (global resolution changes), but lacks explicit when-not guidance, prerequisites (e.g., connection state), or named alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LarsCanGit/OBS-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server