Skip to main content
Glama

Canva

by com.canva.mcp
OverviewDiscussionsAdmin

Search Folders

search-folders
Read-only

Find or browse Canva folders the user owns or that are shared with them.

Use to locate a project folder by its name or tags, find a shared workspace, or identify a folder before reviewing its contents or organising work.

Not for finding designs, images, or subfolders within a known folder.

Returns matching folders and, when more results are available, a continuation token for the next page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of folders to return per page.
queryNoText to match against folder names and tags. Omit to browse all of the user's available folders.
ownershipNoWhich folders to return. Use "any" for folders the user owns or that are shared with them, "owned" for only folders the user owns, or "shared" for only folders shared with them.
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 search query and ownership filter. 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 search query and ownership filter. Omit for the first page."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of folders to return per query"New value: +"Maximum number of folders to return per page."
    • changedInput schema / properties / ownership / description
      Previous value: -"Filter folders by ownership type: 'any' (default), 'owned' (user-owned only), or 'shared' (shared with user only)"New value: +"Which folders to return. Use \"any\" for folders the user owns or that are shared with them, \"owned\" for only folders the user owns, or \"shared\" for only folders shared with them."
    • changedInput schema / properties / query / description
      Previous value: -"Search query to match against folder names and tags"New value: +"Text to match against folder names and tags. Omit to browse all of the user's available folders."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and non-destructive behavior; the description adds value by disclosing the output behavior: 'Returns matching folders and, when more results are available, a continuation token for the next page'. It also confirms the scope of owned/shared folders, but does not mention ordering or result limits beyond the schema.

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?

Four sentences, front-loaded with the core purpose and then exclusions and return behavior. There is no filler, and every sentence earns its place.

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 read-only search tool with annotations, 100% schema coverage on parameters, and no output schema, the description is complete: it covers scope, use cases, exclusions, and pagination. No essential information for choosing or calling it correctly is missing.

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 mostly restates concepts already in the schema (matching by names/tags, owned/shared scope, continuation token). It does not add meaningfully new parameter semantics beyond what the schema provides.

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?

Description opens with a specific verb+resource: 'Find or browse Canva folders the user owns or that are shared with them'. It distinguishes itself from siblings by explicitly stating it is 'Not for finding designs, images, or subfolders', which separates it from search-designs and list-folder-items.

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?

It gives concrete use cases ('locate a project folder by name or tags', 'find a shared workspace', 'identify a folder before reviewing contents') and clear when-not-to-use guidance. It stops short of naming the sibling tool to choose instead, so the routing is slightly less explicit than a 5.

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