AskEditor

Set canvas aspect ratio

set_canvas_aspect_ratio

[write] Set the PROJECT / EXPORT canvas aspect ratio — the frame the preview, every rendered asset and the composite export all use. Use whenever the deliverable's shape (16:9, 9:16 or 1:1) differs from the canvas, before making or rendering graphics, which render at the canvas size. It does not re-fit existing clips (use set_clip_transform). Answers with aspectRatio and the exact width and height to design against. Related: get_timeline, set_clip_transform, render_all_assets. Full docs: load_skill with tools: [name].

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": {
      "project_id": "<project_id>",
      "aspectRatio": "<aspectRatio>"
    },
    "name": "set_canvas_aspect_ratio"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes	The AskEditor project this acts on (from list_projects).
`aspectRatio`	Yes	The canvas shape.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare write, non-destructive, non-open-world; the description adds real value by disclosing that existing clips are not re-fitted and that the response returns aspectRatio plus exact width/height. It does not address the idempotentHint=false annotation, which is notable for a tool that appears to set a single value, so a caller can't tell whether a repeat call is harmless; that gap keeps it below 5.

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?

Front-loaded with the write marker and the core statement, then usage, then exclusions, then return value. Dense but nearly every clause earns its place; the "before making or rendering graphics" clause slightly repeats the render-size point and the docs pointer is boilerplate.

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

Completeness5/5

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

For a 2-parameter write tool with no output schema, the description covers effect, scope, non-effects, sibling routing, and what the call answers with. An agent has everything needed to call it correctly and interpret the result.

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 coverage is 100% and the aspectRatio enum is documented, so the schema already carries parameter meaning. The description clarifies the canvas concept and that the returned width/height are the design targets, but adds no syntax or per-value guidance beyond the schema; baseline 3 is appropriate.

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?

Specific verb+resource ("Set the PROJECT / EXPORT canvas aspect ratio") with the affected scope spelled out: preview, every rendered asset, and the composite export. It is clearly distinguishable from set_clip_transform and set_export_settings, which govern different concerns.

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

Usage Guidelines5/5

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

Explicit trigger ("Use whenever the deliverable's shape ... differs from the canvas, before making or rendering graphics") plus an explicit exclusion and named alternative ("It does not re-fit existing clips (use set_clip_transform)"). Both the when and the when-not are stated.

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

All AskEditor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?