Skip to main content
Glama

update-action

Modify existing comment text on Trello cards to keep project discussions current and accurate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionIdYesID of the action to update
textYesNew text content for the comment action

Implementation Reference

  • The handler function for the 'update-action' tool. It sends a PUT request to the Trello API to update the text content of a comment action, handling credentials check and errors.
    async ({ actionId, text }) => {
    	try {
    		if (!credentials.apiKey || !credentials.apiToken) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: 'Trello API credentials are not configured',
    					},
    				],
    				isError: true,
    			};
    		}
    
    		const response = await fetch(
    			`https://api.trello.com/1/actions/${actionId}?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    			{
    				method: 'PUT',
    				headers: {
    					'Content-Type': 'application/json',
    				},
    				body: JSON.stringify({
    					text,
    				}),
    			}
    		);
    		const data = await response.json();
    
    		return {
    			content: [
    				{
    					type: 'text',
    					text: JSON.stringify(data),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error updating action: ${error}`,
    				},
    			],
    			isError: true,
    		};
    	}
    }
  • Zod input schema for 'update-action' tool, requiring actionId (string) and text (string).
    {
    	actionId: z.string().describe('ID of the action to update'),
    	text: z.string().describe('New text content for the comment action'),
    },
  • Direct registration of the 'update-action' tool using McpServer.tool(), including schema and inline handler within registerActionsTools function.
    server.tool(
    	'update-action',
    	{
    		actionId: z.string().describe('ID of the action to update'),
    		text: z.string().describe('New text content for the comment action'),
    	},
    	async ({ actionId, text }) => {
    		try {
    			if (!credentials.apiKey || !credentials.apiToken) {
    				return {
    					content: [
    						{
    							type: 'text',
    							text: 'Trello API credentials are not configured',
    						},
    					],
    					isError: true,
    				};
    			}
    
    			const response = await fetch(
    				`https://api.trello.com/1/actions/${actionId}?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    				{
    					method: 'PUT',
    					headers: {
    						'Content-Type': 'application/json',
    					},
    					body: JSON.stringify({
    						text,
    					}),
    				}
    			);
    			const data = await response.json();
    
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error updating action: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • src/index.ts:92-92 (registration)
    Top-level call to registerActionsTools which includes the 'update-action' tool registration.
    registerActionsTools(server, credentials);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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