Skip to main content
Glama
nulab

Backlog MCP Server

mark_notification_as_read

Mark a specific notification as read using its ID to clear unread alerts in your Backlog account.

Instructions

Mark a notification as read

Input Schema

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

Implementation Reference

  • The main tool definition including the handler function that executes the tool logic. The handler calls backlog.markAsReadNotification(id) to mark a notification as read.
    export const markNotificationAsReadTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof markNotificationAsReadSchema>,
      (typeof MarkNotificationAsReadResultSchema)['shape']
    > => {
      return {
        name: 'mark_notification_as_read',
        description: t(
          'TOOL_MARK_NOTIFICATION_AS_READ_DESCRIPTION',
          'Mark a notification as read'
        ),
        schema: z.object(markNotificationAsReadSchema(t)),
        outputSchema: MarkNotificationAsReadResultSchema,
        handler: async ({ id }) => {
          await backlog.markAsReadNotification(id);
          return {
            success: true,
            message: `Notification ${id} marked as read`,
          };
        },
      };
    };
  • Input schema (markNotificationAsReadSchema) defining 'id' as a required number, and output schema (MarkNotificationAsReadResultSchema) defining 'success' boolean and 'message' string.
    const markNotificationAsReadSchema = buildToolSchema((t) => ({
      id: z
        .number()
        .describe(
          t('TOOL_MARK_NOTIFICATION_AS_READ_ID', 'Notification ID to mark as read')
        ),
    }));
    
    export const MarkNotificationAsReadResultSchema = z.object({
      success: z.boolean(),
      message: z.string(),
    });
  • The tool is registered as part of the 'notifications' toolset in the tools.ts registration file. It's instantiated at line 173 (markNotificationAsReadTool(backlog, helper)).
        {
          name: 'notifications',
          description: 'Tools for managing user notifications.',
          enabled: false,
          tools: [
            getNotificationsTool(backlog, helper),
            getNotificationsCountTool(backlog, helper),
            resetUnreadNotificationCountTool(backlog, helper),
            markNotificationAsReadTool(backlog, helper),
          ],
        },
      ],
    };
  • Import statement for markNotificationAsReadTool in the tools.ts registration file.
    import { markNotificationAsReadTool } from './markNotificationAsRead.js';
  • The buildToolSchema helper function used to define the tool's input schema with translation support.
    export const buildToolSchema = <T extends z.ZodRawShape>(
      fn: (t: TranslationHelper['t']) => T
    ) => fn;
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only states the basic mutation but does not disclose side effects, permissions required, reversibility, or impact on other notifications. Minimal behavioral 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.

Conciseness4/5

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

The description is a single, succinct sentence with no extraneous text. It is front-loaded and efficient, though it could incorporate a bit more context without becoming verbose.

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 simple tool with no output schema and one required parameter, the description covers the basic action. However, it fails to address the existence of sibling tools like 'mark_watching_as_read' and does not explain the broader workflow or implications of marking a notification read.

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% coverage; both parameters are described in the schema itself. The description adds no additional semantic meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 the resource ('a notification as read'), making the purpose immediately understandable. However, it does not differentiate this tool from siblings like 'mark_watching_as_read'.

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 given on when to use this tool versus alternatives such as 'get_notifications' or 'mark_watching_as_read'. There is no mention of prerequisites or context.

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