Skip to main content
Glama

move_card

Move a GitHub card to a specified position or column by providing the card ID, target position, and optional column ID for organization.

Instructions

Move a card to a different position or column

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idYesThe unique identifier of the card
column_idNoThe column ID to move the card to
positionYesThe position of the card (top, bottom, or after:<card_id>)

Implementation Reference

  • The core handler function that executes the move_card tool logic by making a POST request to GitHub's API to move the project card.
    export async function moveCard(cardId: number, position: string, columnId?: number) {
        try {
            const url = `https://api.github.com/projects/columns/cards/${cardId}/moves`;
    
            const payload: Record<string, any> = {
                position: position
            };
    
            if (columnId) {
                payload.column_id = columnId;
            }
    
            await githubRequest(url, {
                method: 'POST',
                body: payload,
                headers: {
                    'Accept': 'application/vnd.github.inertia-preview+json'
                }
            });
    
            return { success: true };
        } catch (error) {
            if (error instanceof GitHubError) {
                throw error;
            }
    
            throw new GitHubError(`Failed to move card: ${(error as Error).message}`, 500, { error: (error as Error).message });
        }
    }
  • Zod input schema for the move_card tool defining parameters: card_id, position, and optional column_id.
    export const MoveCardSchema = z.object({
        card_id: z.number().describe("The unique identifier of the card"),
        position: z.enum(["top", "bottom"]).or(z.string().regex(/^after:\d+$/)).describe("The position of the card (top, bottom, or after:<card_id>)"),
        column_id: z.number().optional().describe("The column ID to move the card to"),
    });
  • index.ts:255-259 (registration)
    Registration of the move_card tool in the MCP server's list of tools, including name, description, and input schema reference.
    {
      name: "move_card",
      description: "Move a card to a different position or column",
      inputSchema: zodToJsonSchema(projects.MoveCardSchema),
    },
  • Dispatcher case in the central CallToolRequest handler that parses arguments and calls the moveCard function.
    case "move_card": {
      const args = projects.MoveCardSchema.parse(request.params.arguments);
      const result = await projects.moveCard(
        args.card_id,
        args.position,
        args.column_id
      );
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
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 the action ('move') but doesn't describe what happens during the move (e.g., whether it's atomic, if it affects other cards, permission requirements, or error conditions). For a mutation tool with zero annotation coverage, this is a significant gap in transparency about its behavior and side effects.

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 with zero waste—it directly states the tool's purpose without redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly. Every word earns its place by conveying essential information.

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 the tool's complexity (a mutation with 3 parameters) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, side effects, or return values, which are critical for safe and effective use. For a tool that modifies data, this minimal description leaves significant gaps in understanding its full context.

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%, so the schema already documents all three parameters (card_id, column_id, position) with their types and constraints. The description adds no additional meaning beyond what's in the schema—it doesn't explain parameter interactions (e.g., column_id is optional) or provide examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('move') and resource ('card') with the specific action of repositioning it ('to a different position or column'). It distinguishes from sibling tools like 'delete_card' or 'list_column_cards' by focusing on relocation rather than deletion or listing. However, it doesn't explicitly differentiate from similar tools like 'update_project_v2_item_field' which might also affect card positions.

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 card and column IDs), when not to use it (e.g., for creating cards), or direct alternatives among siblings like 'update_project_v2_item_field' for similar positioning tasks. Usage is implied by the action but not explicitly contextualized.

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/tuanle96/mcp-github'

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