Skip to main content
Glama
nulab

Backlog MCP Server

add_watching

Add a watcher to a Backlog issue using its key or ID, with optional note and organization.

Instructions

Adds a new watch to an issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdOrKeyYesIssue ID or issue key (e.g., 1234 or "PROJECT-123")
noteNoOptional note for the watch
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The main handler function for the 'add_watching' tool. It takes a Backlog client and TranslationHelper, returns a ToolDefinition with name 'add_watching', and the handler calls backlog.postWatchingListItem() with issueIdOrKey and note parameters.
    export const addWatchingTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof addWatchingSchema>,
      (typeof WatchingListItemSchema)['shape']
    > => {
      return {
        name: 'add_watching',
        description: t(
          'TOOL_ADD_WATCHING_DESCRIPTION',
          'Adds a new watch to an issue'
        ),
        schema: z.object(addWatchingSchema(t)),
        outputSchema: WatchingListItemSchema,
        handler: async ({ issueIdOrKey, note }) =>
          backlog.postWatchingListItem({
            issueIdOrKey,
            note,
          }),
      };
    };
  • Input schema definition for the 'add_watching' tool. Defines 'issueIdOrKey' (number | string, required) and 'note' (string, optional, defaults to empty string).
    const addWatchingSchema = buildToolSchema((t) => ({
      issueIdOrKey: z
        .union([z.number(), z.string()])
        .describe(
          t(
            'TOOL_ADD_WATCHING_ISSUE_ID_OR_KEY',
            'Issue ID or issue key (e.g., 1234 or "PROJECT-123")'
          )
        ),
      note: z
        .string()
        .describe(t('TOOL_ADD_WATCHING_NOTE', 'Optional note for the watch'))
        .optional()
        .default(''),
    }));
  • Output/output schema for the 'add_watching' tool – WatchingListItemSchema. Defines the shape of the response object (id, resourceAlreadyRead, note, type, issue, lastContentUpdated, created, updated).
    export const WatchingListItemSchema = z.object({
      id: z.number(),
      resourceAlreadyRead: z.boolean(),
      note: z.string(),
      type: z.string(),
      issue: IssueSchema,
      lastContentUpdated: z.string(),
      created: z.string(),
      updated: z.string(),
    });
  • Registration of the 'add_watching' tool within the 'issue' toolset. The toolset is named 'issue' and groups issue-related tools together (enabled: false).
      getWatchingListItemsTool(backlog, helper),
      getWatchingListCountTool(backlog, helper),
      addWatchingTool(backlog, helper),
      updateWatchingTool(backlog, helper),
      deleteWatchingTool(backlog, helper),
      markWatchingAsReadTool(backlog, helper),
      getVersionMilestoneListTool(backlog, helper),
      addVersionMilestoneTool(backlog, helper),
      updateVersionMilestoneTool(backlog, helper),
      deleteVersionTool(backlog, helper),
    ],
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. It fails to mention side effects (e.g., notifications), required permissions, or behavior on duplicate watches, leaving significant gaps for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no extraneous words, but its brevity sacrifices behavioral detail. Appropriate for a simple operation, though could be slightly more informative without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the schema is well-documented and no output schema exists, the description adequately covers the basic purpose but omits behavioral context (e.g., return value, side effects) that would complete the picture for the agent.

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% with clear parameter descriptions (e.g., issueIdOrKey format, hint for organization to use list_organizations). The description adds no extra meaning, so baseline 3 is appropriate.

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 'Adds a new watch to an issue' uses a specific verb ('adds') and resource ('watch'), clearly distinguishing it from sibling tools like add_issue or add_issue_comment which operate on different resources.

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 on when to use this tool versus alternatives like update_watching or delete_watching, nor any prerequisites or context for using the add 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/nulab/backlog-mcp-server'

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