Skip to main content
Glama

update_task

Modify existing task details in FluentBoards project management, including title, description, or stage assignment, to keep project workflows current.

Instructions

Update an existing task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
task_idYesTask ID
titleNoNew task title
descriptionNoNew task description
stage_idNoNew stage ID

Implementation Reference

  • The handler function for the update_task tool. It destructures the arguments, conditionally makes PUT API requests to update the task's title, description, or stage_id, and returns the formatted response.
    async (args) => {
      const { board_id, task_id, title, description, stage_id } = args;
    
      let response;
      
      // Update title if provided
      if (title) {
        response = await api.put(
          `/projects/${board_id}/tasks/${task_id}`,
          { property: 'title', value: title }
        );
      }
    
      // Update description if provided
      if (description) {
        response = await api.put(
          `/projects/${board_id}/tasks/${task_id}`,
          { property: 'description', value: formatText(description) }
        );
      }
    
      // Update stage if provided
      if (stage_id) {
        response = await api.put(
          `/projects/${board_id}/tasks/${task_id}`,
          { property: 'stage_id', value: stage_id }
        );
      }
    
      if (!response) {
        throw new Error('No properties provided for update');
      }
    
      return formatResponse(response.data);
    }
  • Zod schema defining the input parameters for the update_task tool, matching the inline schema used in registration.
    export const UpdateTaskSchema = z.object({
      board_id: z.number().int().positive(),
      task_id: z.number().int().positive(),
      title: z.string().optional(),
      description: z.string().optional(),
      stage_id: z.number().int().positive().optional(),
    });
  • Registers the update_task tool on the MCP server using server.tool(), providing description, input schema, and handler.
    server.tool(
      "update_task",
      "Update an existing task",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        task_id: z.number().int().positive().describe("Task ID"),
        title: z.string().optional().describe("New task title"),
        description: z.string().optional().describe("New task description"),
        stage_id: z.number().int().positive().optional().describe("New stage ID"),
      },
      async (args) => {
        const { board_id, task_id, title, description, stage_id } = args;
    
        let response;
        
        // Update title if provided
        if (title) {
          response = await api.put(
            `/projects/${board_id}/tasks/${task_id}`,
            { property: 'title', value: title }
          );
        }
    
        // Update description if provided
        if (description) {
          response = await api.put(
            `/projects/${board_id}/tasks/${task_id}`,
            { property: 'description', value: formatText(description) }
          );
        }
    
        // Update stage if provided
        if (stage_id) {
          response = await api.put(
            `/projects/${board_id}/tasks/${task_id}`,
            { property: 'stage_id', value: stage_id }
          );
        }
    
        if (!response) {
          throw new Error('No properties provided for update');
        }
    
        return formatResponse(response.data);
      }
    );
  • src/index.ts:23-23 (registration)
    Top-level call to registerTaskTools which includes the update_task tool registration.
    registerTaskTools(server);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update an existing task' implies a mutation operation but doesn't specify required permissions, whether changes are reversible, error handling, or response format. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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 extremely concise with just three words, front-loading the essential information with zero wasted text. Every word earns its place, making it efficient though potentially under-specified.

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?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens during updates, what fields are optional versus required beyond the schema, or what the tool returns. The context demands more completeness than this minimal description provides.

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 fully documents all 5 parameters. The description adds no additional meaning about parameters beyond what's in the schema, but since the schema provides complete coverage, the baseline score of 3 is appropriate.

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

Purpose3/5

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

The description 'Update an existing task' clearly states the action (update) and resource (task), but it's vague about what aspects can be updated and doesn't differentiate from sibling tools like 'change_task_status' or 'edit_label'. It provides basic purpose but lacks specificity.

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 like 'change_task_status' for status updates or 'edit_label' for label modifications. The description offers no context about prerequisites, exclusions, or appropriate scenarios for this update operation.

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/danieliser/fluent-boards-mcp-server'

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