Skip to main content
Glama
diegofornalha

MCP Server Trello

get_recent_activity

Track and retrieve recent actions on a Trello board to monitor updates, manage tasks, and stay informed with customizable activity limits using the MCP Server Trello integration.

Instructions

Fetch recent activity on the Trello board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of activities to fetch (default: 10)

Implementation Reference

  • MCP tool handler for get_recent_activity that validates input and delegates to TrelloClient.
    case 'get_recent_activity': {
      const validArgs = validateGetRecentActivityRequest(args);
      const activity = await this.trelloClient.getRecentActivity(validArgs.limit);
      return {
        content: [{ type: 'text', text: JSON.stringify(activity, null, 2) }],
      };
    }
  • Validation function for get_recent_activity input parameters.
    export function validateGetRecentActivityRequest(args: Record<string, unknown>): { limit?: number } {
      return {
        limit: validateOptionalNumber(args.limit),
      };
    }
  • src/index.ts:84-97 (registration)
    Registration of the get_recent_activity tool with name, description, and input schema.
    {
      name: 'get_recent_activity',
      description: 'Fetch recent activity on the Trello board',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Number of activities to fetch (default: 10)',
          },
        },
        required: [],
      },
    },
  • Implementation of getRecentActivity method in TrelloClient that fetches recent actions from the Trello API.
    async getRecentActivity(limit: number = 10): Promise<TrelloAction[]> {
      console.error(`[TrelloClient] Getting recent activity for board: ${this.config.boardId} (limit: ${limit})`);
      return this.handleRequest(async () => {
        const response = await this.axiosInstance.get(`/boards/${this.config.boardId}/actions`, {
          params: { limit },
        });
        return response.data;
      });
    }
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 'fetch' implies a read operation, but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'recent activity' entails (e.g., time range, types of activities). This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete for a tool that fetches data. It lacks details on return format, error cases, or behavioral traits, which are crucial for an agent to use the tool effectively in context with its siblings.

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 description coverage is 100%, with the parameter 'limit' fully documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as constraints or examples, so it meets the baseline for high schema coverage without extra value.

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 action ('fetch') and resource ('recent activity on the Trello board'), making the purpose understandable. It doesn't explicitly distinguish from siblings like 'get_cards_by_list_id' or 'get_my_cards', which also retrieve data but focus on different resources, so it misses full sibling differentiation.

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 is provided on when to use this tool versus alternatives. The description doesn't mention context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone, which is insufficient for optimal selection.

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

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

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