Skip to main content
Glama
nulab

Backlog MCP Server

update_project

Modify existing project details in Backlog, including name, settings, and status, to maintain accurate project management records.

Instructions

Updates an existing project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe numeric ID of the project (e.g., 12345)
projectKeyNoThe key of the project (e.g., 'PROJECT')
nameNoProject name
keyNoProject key
chartEnabledNoWhether to enable chart
subtaskingEnabledNoWhether to enable subtasking
projectLeaderCanEditProjectLeaderNoWhether project leaders can edit other project leaders
textFormattingRuleNoText formatting rule
archivedNoWhether to archive the project

Implementation Reference

  • The asynchronous handler function for the 'update_project' tool. It resolves the project ID or key using resolveIdOrKey and calls backlog.patchProject with the resolved project ID and update parameters.
    handler: async ({ projectId, projectKey, ...param }) => {
      const result = resolveIdOrKey(
        'project',
        { id: projectId, key: projectKey },
        t
      );
      if (!result.ok) {
        throw result.error;
      }
      return backlog.patchProject(result.value, param);
    },
  • Zod schema definition for the input parameters of the 'update_project' tool, including optional projectId, projectKey, name, key, and various project settings.
    const updateProjectSchema = buildToolSchema((t) => ({
      projectId: z
        .number()
        .optional()
        .describe(
          t(
            'TOOL_UPDATE_PROJECT_PROJECT_ID',
            'The numeric ID of the project (e.g., 12345)'
          )
        ),
      projectKey: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_UPDATE_PROJECT_PROJECT_KEY',
            "The key of the project (e.g., 'PROJECT')"
          )
        ),
      name: z
        .string()
        .optional()
        .describe(t('TOOL_UPDATE_PROJECT_NAME', 'Project name')),
      key: z
        .string()
        .optional()
        .describe(t('TOOL_UPDATE_PROJECT_KEY', 'Project key')),
      chartEnabled: z
        .boolean()
        .optional()
        .describe(
          t('TOOL_UPDATE_PROJECT_CHART_ENABLED', 'Whether to enable chart')
        ),
      subtaskingEnabled: z
        .boolean()
        .optional()
        .describe(
          t(
            'TOOL_UPDATE_PROJECT_SUBTASKING_ENABLED',
            'Whether to enable subtasking'
          )
        ),
      projectLeaderCanEditProjectLeader: z
        .boolean()
        .optional()
        .describe(
          t(
            'TOOL_UPDATE_PROJECT_LEADER_CAN_EDIT',
            'Whether project leaders can edit other project leaders'
          )
        ),
      textFormattingRule: z
        .enum(['backlog', 'markdown'])
        .optional()
        .describe(t('TOOL_UPDATE_PROJECT_TEXT_FORMATTING', 'Text formatting rule')),
      archived: z
        .boolean()
        .optional()
        .describe(
          t('TOOL_UPDATE_PROJECT_ARCHIVED', 'Whether to archive the project')
        ),
    }));
  • The 'updateProjectTool' is invoked and registered within the 'project' toolset group in the allTools function.
    updateProjectTool(backlog, helper),
  • Import statement for the updateProjectTool from its implementation file.
    import { updateProjectTool } from './updateProject.js';
  • The full tool definition function that creates and exports the 'update_project' tool, including name, description, schema, output schema, and handler.
    export const updateProjectTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof updateProjectSchema>,
      (typeof ProjectSchema)['shape']
    > => {
      return {
        name: 'update_project',
        description: t(
          'TOOL_UPDATE_PROJECT_DESCRIPTION',
          'Updates an existing project'
        ),
        schema: z.object(updateProjectSchema(t)),
        outputSchema: ProjectSchema,
        handler: async ({ projectId, projectKey, ...param }) => {
          const result = resolveIdOrKey(
            'project',
            { id: projectId, key: projectKey },
            t
          );
          if (!result.ok) {
            throw result.error;
          }
          return backlog.patchProject(result.value, param);
        },
      };
    };
Behavior1/5

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

With no annotations provided, the description carries full burden but offers zero behavioral disclosure. It doesn't indicate whether this is a mutation requiring specific permissions, what happens on success/failure, if changes are reversible, or any rate limits. 'Updates' implies a write operation, but no safety or side-effect information is given.

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 at just three words, with zero wasted language. It's front-loaded with the core action, though this brevity comes at the cost of completeness. Every word earns its place by stating the basic operation.

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 9 parameters, no annotations, and no output schema, the description is severely inadequate. It doesn't explain what constitutes a valid update, which fields are optional/required together, what the tool returns, or error conditions. The 100% schema coverage helps, but the description fails to provide necessary contextual guidance for proper use.

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 9 parameters. The description adds no parameter-specific information beyond the generic 'updates an existing project' statement. This meets the baseline of 3 since the schema does the heavy lifting, but the description provides no additional context about parameter interactions or required subsets.

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

Purpose2/5

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

The description 'Updates an existing project' is a tautology that restates the tool name 'update_project' without adding meaningful specificity. It doesn't distinguish what kind of project or what aspects can be updated, nor does it differentiate from sibling tools like 'update_issue' or 'update_pull_request' beyond the resource name.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing project ID), when to choose this over 'add_project' for creation, or how it differs from other update tools like 'update_issue' in the sibling list.

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/nulab/backlog-mcp-server'

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