Skip to main content
Glama
nulab

Backlog MCP Server

mark_notification_as_read

Mark notifications as read in Backlog to clear alerts and update your notification status.

Instructions

Mark a notification as read

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNotification ID to mark as read

Implementation Reference

  • The handler function that executes the tool logic: marks the notification as read using the Backlog client and returns a success message.
    handler: async ({ id }) => {
      await backlog.markAsReadNotification(id);
      return {
        success: true,
        message: `Notification ${id} marked as read`,
      };
    },
  • Input schema (notification id: number) and output schema (success: boolean, 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(),
    });
  • Factory function exporting the tool definition with name, description, schemas, and handler.
    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`,
          };
        },
      };
    };
  • Registration of the tool within the 'notifications' toolset group in the main tools export.
    {
      name: 'notifications',
      description: 'Tools for managing user notifications.',
      enabled: false,
      tools: [
        getNotificationsTool(backlog, helper),
        getNotificationsCountTool(backlog, helper),
        resetUnreadNotificationCountTool(backlog, helper),
        markNotificationAsReadTool(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. While 'mark as read' implies a state-changing operation, the description doesn't disclose important behavioral traits: whether this requires specific permissions, whether the change is reversible, what happens if the notification is already read, or what the expected response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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 maximally concise at just 5 words, with zero wasted language. It's front-loaded with the essential action and resource, making it immediately clear what the tool does without any unnecessary elaboration.

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 no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after marking as read, whether there are side effects, what permissions are required, or how this interacts with other notification tools. The presence of sibling tools like 'get_notifications' and 'reset_unread_notification_count' suggests this is part of a notification system, but the description provides no integration context.

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 schema description coverage is 100% (the 'id' parameter is fully documented in the schema), so the baseline is 3. The description doesn't add any parameter semantics beyond what's already in the schema - it doesn't explain where to get the notification ID from, what format it should be in, or provide any additional context about the parameter.

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 'Mark a notification as read' clearly states the action (mark as read) and target resource (notification), providing a specific verb+resource combination. However, it doesn't distinguish this tool from the sibling 'mark_watching_as_read' tool, which performs a similar marking-as-read operation on a different resource type.

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?

The description provides no guidance about when to use this tool versus alternatives. There's no mention of prerequisites (like needing to fetch notifications first), no indication of when this operation is appropriate versus other notification management tools, and no reference to the sibling 'mark_watching_as_read' tool that performs a similar function on a different resource.

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