Skip to main content
Glama

mark_notification_as_read

Update a specific notification's status to 'read' using its ID, ensuring cleared alerts and streamlined project management workflows in Backlog.

Instructions

Mark a notification as read

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNotification ID to mark as read

Implementation Reference

  • The asynchronous handler function that marks the specified notification as read using the Backlog API and returns a success response.
    handler: async ({ id }) => { await backlog.markAsReadNotification(id); return { success: true, message: `Notification ${id} marked as read`, }; },
  • Zod schemas defining the input parameter (notification ID as number) and output structure (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(), });
  • Registers the markNotificationAsReadTool as part of the 'notifications' toolset group by calling the factory function with backlog and translation helper.
    tools: [ getNotificationsTool(backlog, helper), getNotificationsCountTool(backlog, helper), resetUnreadNotificationCountTool(backlog, helper), markNotificationAsReadTool(backlog, helper), ], },

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