Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai

update_list

Rename Trello lists to organize project workflows by providing the list ID and new name.

Instructions

Updates the name of a list.

Args:
    list_id (str): The ID of the list to update.
    name (str): The new name for the list.

Returns:
    TrelloList: The updated list object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
nameYes

Implementation Reference

  • MCP tool handler for 'update_list' that calls the ListService to update a Trello list's name.
    async def update_list(ctx: Context, list_id: str, name: str) -> TrelloList:
        """Updates the name of a list.
    
        Args:
            list_id (str): The ID of the list to update.
            name (str): The new name for the list.
    
        Returns:
            TrelloList: The updated list object.
        """
        try:
            logger.info(f"Updating list {list_id} with new name: {name}")
            result = await service.update_list(list_id, name)
            logger.info(f"Successfully updated list: {list_id}")
            return result
        except Exception as e:
            error_msg = f"Failed to update list: {str(e)}"
            logger.error(error_msg)
            await ctx.error(error_msg)
            raise
  • Registration of the 'update_list' tool in the MCP server.
    mcp.add_tool(list.update_list)
  • Helper service method that makes the Trello API call to update the list name.
    async def update_list(self, list_id: str, name: str) -> TrelloList:
        """Updates the name of a list.
    
        Args:
            list_id (str): The ID of the list to update.
            name (str): The new name for the list.
    
        Returns:
            TrelloList: The updated list object.
        """
        response = await self.client.PUT(f"/lists/{list_id}", data={"name": name})
        return TrelloList(**response)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't cover critical aspects like required permissions, whether changes are reversible, error conditions, or rate limits. The mention of returning 'The updated list object' hints at output but lacks detail on format or structure.

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?

The description is highly concise and well-structured. It starts with a clear purpose statement, followed by organized sections for Args and Returns, each with bullet-like formatting. Every sentence earns its place by providing essential information without redundancy or fluff.

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?

Given the tool's moderate complexity (a mutation with 2 parameters), no annotations, and no output schema, the description is partially complete. It covers the purpose and parameters effectively but lacks behavioral context (e.g., side effects, error handling) and detailed output information beyond a high-level return type ('TrelloList'). This leaves gaps for the agent to operate safely and efficiently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant value beyond the input schema, which has 0% description coverage. It explicitly documents both parameters (list_id and name) with clear semantics: list_id identifies the target list, and name specifies the new value. This compensates fully for the schema's lack of descriptions, making the parameters well-understood.

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's purpose: 'Updates the name of a list.' This specifies the verb ('Updates') and resource ('list'), with the action focused on modifying the name. However, it doesn't explicitly differentiate from sibling tools like 'update_card' or 'update_checklist', which have similar naming patterns but target different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid list_id), exclusions, or comparisons to siblings like 'update_card' or 'update_checklist'. The agent must infer usage from the tool name and parameters alone.

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/m0xai/trello-mcp-server'

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