Skip to main content
Glama

Canva

by com.canva.mcp
OverviewDiscussionsAdmin

List Folder Items

list-folder-items
Read-only

Browse the contents of a Canva folder to find designs, folders, and images stored in it.

Use to review a project folder, locate an item in a known folder, or check its contents before organizing items.

Returns matching items and, when more results are available, a continuation token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sort_byNoOrder the results by creation date, last modified date, or title, in ascending or descending order.
folder_idYesID of the Canva folder to list. Use "root" to list items at the top level.
item_typesNoTypes of items to return. Omit to return designs, folders, and images.
user_intentNoMandatory description of what the user is trying to accomplish with this tool call. This should always be provided by LLM clients. Please keep it concise (255 characters or less recommended).
continuationNoExact continuation token returned by the previous call with the same folder, filters, and sort order. Omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / continuation / description
      Previous value: -"\n            Pagination token for the current search context.\n\n            CRITICAL RULES:\n            - ONLY set this parameter if the previous response included a continuation token.\n            - If no continuation token was returned → OMIT this parameter completely. NEVER EVER fabricate a token.\n            - Do not set to null, empty string, or any other value when no token was provided.\n\n            Usage:\n            - First request: omit this parameter\n            - Previous response had continuation token: use that exact token\n            - Previous response had NO continuation token: omit this parameter\n            - New search query: omit this parameter\n            "New value: +"Exact continuation token returned by the previous call with the same folder, filters, and sort order. Omit for the first page."
    • changedInput schema / properties / folder_id / description
      Previous value: -"ID of the folder to list items from. Use 'root' to list items at the top level"New value: +"ID of the Canva folder to list. Use \"root\" to list items at the top level."
    • changedInput schema / properties / item_types / description
      Previous value: -"Filter items by type. Can be 'design', 'folder', or 'image'"New value: +"Types of items to return. Omit to return designs, folders, and images."
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort the items by creation date, modification date, or title"New value: +"Order the results by creation date, last modified date, or title, in ascending or descending order."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context beyond that: results are filtered ('matching items') and pagination is handled via a continuation token. This helps the agent understand multi-page behavior and that the response shape is a list, not a single object.

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?

Three short sentences with no filler. The core action is front-loaded in sentence one, usage context in sentence two, and the pagination behavior in sentence three. Every sentence earns its place and the description is easy to scan.

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 read-only browse tool, the description covers the essential decision points: what items are returned, when to use it, and how pagination works. With no output schema, some detail about the shape of returned items would be useful, but the annotation-provided safety profile and the clear continuation-token note make this adequate for an agent to call it correctly.

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 the baseline is 3. The description reinforces the item_types parameter by naming designs, folders, and images, and mentions the continuation token that maps to the continuation parameter, but it does not add new semantic meaning beyond what the schema already documents.

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?

The description opens with a specific verb and resource: 'Browse the contents of a Canva folder to find designs, folders, and images stored in it.' This clearly states what the tool does and distinguishes it from sibling search tools like search-designs and search-folders, which find items across folders rather than browsing one known folder. The phrase 'stored in it' further narrows scope to a single folder's contents.

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?

The second sentence gives concrete use cases: 'review a project folder, locate an item in a known folder, or check its contents before organizing items.' This tells an agent when to reach for this tool, and 'known folder' implicitly contrasts with search tools for unknown locations. However, it does not explicitly name alternatives or state when not to use it, so it stops short of full differentiation.

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

All Canva toolsInspect
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