Skip to main content
Glama

XCut AI – Viral Content Research

List canvases

xcut_list_canvases
Read-onlyIdempotent

Use this when you need a canvas id or the user asks what XcutAI canvases (projects) they have, including ones shared with them, newest first. Free. Do not call it just to import a post or write: those tools use the user's "From AI apps" canvas when no canvas is named.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xcut_list_canvases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost canvases to return, 1-100. Default 30.
include_sharedNoAlso list canvases shared with the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond them: 'Free' (cost), 'newest first' (ordering), and shared-canvas inclusion. It does not describe return format or pagination, but for a read list that is minor.

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?

Two tight sentences, front-loaded with the trigger condition, then the exclusion. No wasted words.

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 zero-required-param list tool with full schema coverage and annotations, the description supplies everything needed: what it returns, ordering, scope, cost, and routing to siblings. No output schema is required for this operation.

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%, with both limit and include_shared documented in the schema, so the baseline is 3. The description's 'including ones shared with them' loosely maps to include_shared but adds no syntax or format detail beyond the schema.

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?

States a specific verb+resource ('list canvases (projects)'), plus scoping details ('including ones shared with them, newest first'). It also distinguishes itself from siblings by noting that import/write tools use the 'From AI apps' canvas instead.

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 when-to-use ('when you need a canvas id or the user asks what canvases they have') and when-not-to-use ('Do not call it just to import a post or write'). It names the alternative behavior those other tools use, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources