Skip to main content
Glama
nulab

Backlog MCP Server

mark_watching_as_read

Mark a specified watch as read in Backlog to clear unread notifications for a tracked item.

Instructions

Mark a watch as read

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
watchIdYesWatch ID to mark as read
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The handler function for the 'mark_watching_as_read' tool. It takes a watchId, calls backlog.resetWatchingListItemAsRead(watchId), and returns success/ message.
    export const markWatchingAsReadTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof markWatchingAsReadSchema>,
      (typeof MarkWatchingAsReadResultSchema)['shape']
    > => {
      return {
        name: 'mark_watching_as_read',
        description: t(
          'TOOL_MARK_WATCHING_AS_READ_DESCRIPTION',
          'Mark a watch as read'
        ),
        schema: z.object(markWatchingAsReadSchema(t)),
        outputSchema: MarkWatchingAsReadResultSchema,
        handler: async ({ watchId }) => {
          await backlog.resetWatchingListItemAsRead(watchId);
          return {
            success: true,
            message: `Watch ${watchId} marked as read`,
          };
        },
      };
    };
  • Input schema using buildToolSchema, defining 'watchId' as a required number.
    const markWatchingAsReadSchema = buildToolSchema((t) => ({
      watchId: z
        .number()
        .describe(
          t('TOOL_MARK_WATCHING_AS_READ_WATCH_ID', 'Watch ID to mark as read')
        ),
    }));
  • Output schema (MarkWatchingAsReadResultSchema): success boolean and message string.
    export const MarkWatchingAsReadResultSchema = z.object({
      success: z.boolean(),
      message: z.string(),
    });
  • Import of the markWatchingAsReadTool from its definition file.
    import { markWatchingAsReadTool } from './markWatchingAsRead.js';
  • Registration of markWatchingAsReadTool in the 'issue' toolset.
    markWatchingAsReadTool(backlog, helper),
Behavior1/5

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

The description merely restates the tool name ('Mark a watch as read') without disclosing any behavioral traits such as side effects, reversibility, or authorization requirements. With no annotations to provide safety context, the description fails to inform the agent about the nature of the operation.

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

Conciseness3/5

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

The description is a single sentence with no wasted words, but it is too terse to be informative. It does not add value beyond the tool name, so while concise, it lacks substance.

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 absence of an output schema and annotations, the description does not explain return values or provide context about what a 'watch' is in this system. It fails to compensate for missing structured information, leaving the agent underinformed.

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?

The input schema has 100% description coverage, so the schema already documents both parameters adequately. The description adds no additional meaning beyond what the schema provides, meeting the baseline expectation.

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 action ('mark') and resource ('watch'), and the tool name reinforces this. However, it does not differentiate from sibling tools like mark_notification_as_read, which could cause confusion for an agent.

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. The optional organization parameter is mentioned in the schema but not in the description, and there is no explicit context for when to use this vs mark_notification_as_read or update_watching.

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