Skip to main content
Glama

import-trello-importBoards

Import multiple Trello boards into a Kanban workspace by providing board IDs and workspace public ID.

Instructions

Imports boards from Trello (Tags: Imports)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestBodyYesThe JSON request body.
Behavior2/5

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

No annotations provided, and the description only says 'Imports boards from Trello'. It does not disclose side effects (e.g., creating boards), authorization needs, or other behavioral traits. For a potentially destructive operation, more detail is needed.

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?

The description is very concise, consisting of one sentence and tags. However, it sacrifices informativeness for brevity. It earns a 4 for efficiency but lacks necessary detail.

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

Completeness2/5

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

Given the complexity of an import operation, the description is incomplete. It does not explain return values, the effect on the system, or the relationship with sibling tools like 'import-trello-getBoards'. Also, nested parameters in the schema are not explained.

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%, so the description adds no parameter information beyond what the schema provides. Baseline score of 3 applies as the description does not enhance parameter understanding.

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?

The description clearly states the tool imports boards from Trello, which is a specific verb+resource. However, it does not differentiate from sibling tool 'import-trello-getBoards', which retrieves boards but does not import.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. No mention of prerequisites, such as needing an integration or authorization. The description is too minimal to provide context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AixLabTech/kanbn-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server