Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_remote_discover

Discovers all live tools exposed by the remote Canva MCP server using the active authenticated account, with optional account ID override.

Instructions

Discover all live tools exposed by the remote Canva MCP server (https://mcp.canva.com/mcp) using the active authenticated account.

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": "canva_remote_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoOptional account ID override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden; it does disclose the auth context ('using the active authenticated account') and names the remote endpoint, which are useful behavioral signals. It does not say what happens if the account is unauthenticated, whether the call is read-only/network-bound, or what form the discovered tools take.

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?

One sentence, front-loaded with the verb and resource, with the endpoint URL as the only parenthetical. Nothing is redundant or padded.

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

Completeness3/5

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

The tool is simple (one optional param, no nested objects), but there is no output schema, so the description should at least sketch what 'discovered tools' looks like (names, descriptions, schemas). Auth context is present; return shape and failure behavior are not.

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 coverage is 100% and the single optional account_id is fully documented, so the baseline is 3. The phrase 'using the active authenticated account' usefully clarifies the default that account_id overrides, but adds no format or validity details beyond the schema.

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

Purpose4/5

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

A concrete verb ('Discover') and resource ('all live tools exposed by the remote Canva MCP server'), including the endpoint URL, so the agent knows exactly what this returns. It does not explicitly contrast itself with canva_remote_call, which is the most likely ambiguity given the sibling set.

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

Usage Guidelines3/5

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

Usage is only implied: 'discover all live tools' hints that this precedes actual remote invocation, but the description never states when to use it instead of canva_remote_call or what to do with the discovered list. No prerequisites or exclusions are given.

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