Skip to main content
Glama

get-action-reactions

Retrieve reactions and associated data for a specific Trello action to analyze engagement and feedback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionIdYesID of the action
memberNoInclude member information for reactions
emojiNoInclude emoji information for reactions

Implementation Reference

  • Registration of the 'get-action-reactions' tool using server.tool(). Includes the tool name, Zod input schema, and inline handler function that fetches reactions from Trello API.
    // GET /actions/{id}/reactions - Get reactions for an Action
    server.tool(
    	'get-action-reactions',
    	{
    		actionId: z.string().describe('ID of the action'),
    		member: z.boolean().optional().describe('Include member information for reactions'),
    		emoji: z.boolean().optional().describe('Include emoji information for reactions'),
    	},
    	async ({ actionId, member, emoji }) => {
    		try {
    			if (!credentials.apiKey || !credentials.apiToken) {
    				return {
    					content: [
    						{
    							type: 'text',
    							text: 'Trello API credentials are not configured',
    						},
    					],
    					isError: true,
    				};
    			}
    
    			const url = new URL(`https://api.trello.com/1/actions/${actionId}/reactions`);
    			url.searchParams.append('key', credentials.apiKey);
    			url.searchParams.append('token', credentials.apiToken);
    			if (member !== undefined) url.searchParams.append('member', member.toString());
    			if (emoji !== undefined) url.searchParams.append('emoji', emoji.toString());
    
    			const response = await fetch(url.toString());
    			const data = await response.json();
    
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error getting action reactions: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • The tool handler function. Constructs Trello API URL for action reactions, appends credentials and optional params, fetches data, returns JSON stringified response or error message.
    async ({ actionId, member, emoji }) => {
    	try {
    		if (!credentials.apiKey || !credentials.apiToken) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: 'Trello API credentials are not configured',
    					},
    				],
    				isError: true,
    			};
    		}
    
    		const url = new URL(`https://api.trello.com/1/actions/${actionId}/reactions`);
    		url.searchParams.append('key', credentials.apiKey);
    		url.searchParams.append('token', credentials.apiToken);
    		if (member !== undefined) url.searchParams.append('member', member.toString());
    		if (emoji !== undefined) url.searchParams.append('emoji', emoji.toString());
    
    		const response = await fetch(url.toString());
    		const data = await response.json();
    
    		return {
    			content: [
    				{
    					type: 'text',
    					text: JSON.stringify(data),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error getting action reactions: ${error}`,
    				},
    			],
    			isError: true,
    		};
    	}
    }
  • Input schema using Zod: actionId (string, required), member (boolean, optional), emoji (boolean, optional).
    {
    	actionId: z.string().describe('ID of the action'),
    	member: z.boolean().optional().describe('Include member information for reactions'),
    	emoji: z.boolean().optional().describe('Include emoji information for reactions'),
    },
  • src/index.ts:92-92 (registration)
    Invocation of registerActionsTools function, which registers the get-action-reactions tool (among other actions tools).
    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