Skip to main content
Glama
agrath

Atlassian Trello MCP Server

trello_remove_member_from_card

Remove a member from a Trello card to manage card assignments and streamline workflow. Specify the card and member IDs to revoke access.

Instructions

Remove a member from a Trello card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyNoTrello API key (optional if TRELLO_API_KEY env var is set)
tokenNoTrello API token (optional if TRELLO_TOKEN env var is set)
cardIdYesID or URL of the card
memberIdYesID of the member to remove from the card

Implementation Reference

  • Main handler function that removes a member from a Trello card. Extracts credentials, validates params, calls TrelloClient.removeMemberFromCard(), and returns a formatted response.
    export async function handleTrelloRemoveMemberFromCard(args: unknown) {
      try {
        const { credentials, params } = extractCredentials(args);
        const { cardId, memberId} = validateRemoveMemberFromCard(params);
        const client = new TrelloClient(credentials);
    
        const response = await client.removeMemberFromCard(cardId, memberId);
    
        const result = {
          summary: `Removed member ${memberId} from card ${cardId}`,
          cardId,
          memberId,
          rateLimit: response.rateLimit
        };
    
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
  • Validation schema for the remove_member_from_card tool using Zod. Validates cardId and memberId via trelloIdSchema.
    const validateRemoveMemberFromCard = (args: unknown) => {
      const schema = z.object({
    
        cardId: trelloIdSchema,
        memberId: trelloIdSchema
      });
      return schema.parse(args);
    };
    
    const validateDeleteLabel = (args: unknown) => {
      const schema = z.object({
    
        labelId: trelloIdSchema
      });
      return schema.parse(args);
    };
  • Tool definition object with name 'trello_remove_member_from_card', description, and inputSchema specifying required cardId and memberId parameters.
    export const trelloRemoveMemberFromCardTool: Tool = {
      name: 'trello_remove_member_from_card',
      description: 'Remove a member from a Trello card.',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: {
            type: 'string',
            description: 'Trello API key (optional if TRELLO_API_KEY env var is set)'
          },
          token: {
            type: 'string',
            description: 'Trello API token (optional if TRELLO_TOKEN env var is set)'
          },
          cardId: {
            type: 'string',
            description: 'ID or URL of the card'
          },
          memberId: {
            type: 'string',
            description: 'ID of the member to remove from the card'
          }
        },
        required: ['cardId', 'memberId']
      }
    };
  • TrelloClient method that makes a DELETE request to /cards/{cardId}/idMembers/{memberId} to remove a member from a card.
    async removeMemberFromCard(cardId: string, memberId: string): Promise<TrelloApiResponse<void>> {
      return this.makeRequest<void>(
        `/cards/${cardId}/idMembers/${memberId}`,
        { method: 'DELETE' },
        `Remove member ${memberId} from card ${cardId}`
      );
    }
  • src/server.ts:323-324 (registration)
    Server-side route handler dispatching 'trello_remove_member_from_card' to handleTrelloRemoveMemberFromCard.
    case 'trello_remove_member_from_card':
      return await handleTrelloRemoveMemberFromCard(args);
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the basic operation without mentioning side effects, irreversibility, authentication needs beyond schema, rate limits, or error conditions.

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, concise sentence with no extraneous words. It is well-structured and easy to parse.

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, no output schema, and 4 parameters, the description lacks details about return values, error handling, and post-removal state. It is too minimal for a tool that modifies data.

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% and parameter names/descriptions are self-explanatory. The description adds no extra meaning beyond what the schema already provides, so baseline score of 3 applies.

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

Purpose5/5

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

The description 'Remove a member from a Trello card.' clearly states the action (remove), the resource (member), and the object (card). It is specific and distinguishes from sibling tools like trello_add_member_to_card.

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, no prerequisites, no context about required permissions, and no examples. The input schema defines required parameters but does not offer usage 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/agrath/Trello-Desktop-MCP'

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