Skip to main content
Glama

canvas_items

Retrieves every item on a named canvas in spatial reading order, returning descriptions, paths, and metadata so you can inspect arrangements and then view images with view_inspo.

Instructions

What is on one canvas, in reading order, with each item's description.

Returns paths and metadata, not pictures — pass the paths to view_inspo to actually look at the arrangement.

Order is spatial: top to bottom, then left to right within a row. That matters, because a canvas is an arrangement and the order things were added in says nothing about how they now sit beside each other. Text and sticky notes on the canvas are returned too, in position, since they are often the reason a grouping exists.

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": {
      "canvas": "<canvas>"
    },
    "name": "canvas_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
canvasYesCanvas name, e.g. "Packaging". Case-insensitive. Use list_canvases to see them.
projectNoProject name, if two canvases share a name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it states that return values are paths and metadata rather than images, that ordering is spatial (top-to-bottom then left-to-right) and deliberately not insertion order, and that text and sticky notes are included in position. It omits any mention of permissions, limits, or pagination for large canvases.

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 core answer, then the critical caveat about pictures, then ordering semantics. The third paragraph's explanatory aside ('a canvas is an arrangement...') slightly over-justifies the ordering rule but still earns its place by preventing a wrong assumption about insertion order.

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?

With no output schema, the description must convey the return shape, and it does: item paths plus metadata, positional ordering, and inclusion of text/sticky notes. Missing only secondary details such as response size, pagination, or what per-item metadata fields look like, which a caller might want for large canvases.

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 100%, so both parameters (canvas, project) are already documented in the schema, including case-insensitivity and the disambiguation purpose of project. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema does the work.

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?

Names a specific resource and scope ('What is on one canvas, in reading order, with each item's description') and explicitly contrasts its output with the sibling view_inspo, which returns pictures rather than paths. An agent can distinguish it from view_inspo and describe_item without opening any 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 clear selection rule: use this to learn the arrangement and metadata, then pass the returned paths to view_inspo to look at it. The canvas-name prerequisite routes to list_canvases, though the schema already covers that. No explicit when-not-to-use beyond the view_inspo split.

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