mcp-canva

Overview Schema Source Related Servers Discussions Admin

desktop_scroll

Scrolls the desktop view vertically by the specified amount; positive values move up, enabling screen navigation during Canva desktop tasks.

Instructions

Scroll (positive = up).

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": {
      "amount": "<amount>"
    },
    "name": "desktop_scroll"
  }
}

Input Schema

Name	Required	Description	Default
`x`	No
`y`	No
`amount`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does usefully disclose the direction convention ('positive = up'), which is not derivable from the schema, but it omits scroll units, whether x/y define the scroll target, and what state the action affects.

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

Conciseness3/5

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

The single fragment is front-loaded and wastes no words, but this is under-specification rather than true conciseness; a slightly longer description would earn its place given the undocumented parameters.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the definition is still incomplete for a three-parameter input with zero schema coverage and no annotations describing safety or effects. Coordinate and unit semantics are missing.

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

Parameters2/5

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

Schema description coverage is 0% and there are three parameters (x, y, amount). The description only partially explains 'amount' via its sign convention; x and y are entirely undocumented in both the schema and the description, leaving their role (coordinates? cursor target?) unknown.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Scroll') on the implicitly-named desktop surface, matching the desktop_* sibling family. However, it never says what is being scrolled (window, page, cursor position) or how it differs from desktop_drag, so the purpose is only minimally distinguished from siblings.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as desktop_drag or scroll-at-cursor variants. The only hint of usage is the direction convention in parentheses.

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