Skip to main content
Glama
nulab

Backlog MCP Server

mark_watching_as_read

Mark a Backlog watch notification as read to clear it from your notification list and update your project tracking status.

Instructions

Mark a watch as read

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
watchIdYesWatch ID to mark as read

Implementation Reference

  • The handler function that executes the tool logic: calls backlog.resetWatchingListItemAsRead(watchId) and returns a success response.
    handler: async ({ watchId }) => {
      await backlog.resetWatchingListItemAsRead(watchId);
      return {
        success: true,
        message: `Watch ${watchId} marked as read`,
      };
    },
  • Input schema defining the 'watchId' parameter as a 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 defining the result with success boolean and message string.
    export const MarkWatchingAsReadResultSchema = z.object({
      success: z.boolean(),
      message: z.string(),
    });
  • Registration of the markWatchingAsReadTool in the 'issue' toolset group.
    markWatchingAsReadTool(backlog, helper),
  • The tool factory function that defines and exports the tool with name, description, schema, outputSchema, and handler.
    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`,
          };
        },
      };
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Mark a watch as read' implies a mutation operation, but it doesn't disclose behavioral traits such as required permissions, whether this action is reversible, what happens to the watch after marking (e.g., if it's removed from a list), or error conditions. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral aspects (e.g., side effects, permissions), output format, or error handling. While the schema covers the single parameter, the overall context for safe and effective use is insufficient.

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 description adds no parameter information beyond what's in the schema, which has 100% coverage (the single parameter 'watchId' is fully described as 'Watch ID to mark as read'). With high schema coverage, the baseline is 3, as the description doesn't need to compensate but also doesn't provide additional semantic context like format examples or constraints.

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 watch as read' clearly states the verb ('Mark') and resource ('a watch') with the specific action ('as read'). It distinguishes from siblings like 'add_watching' (create) and 'update_watching' (modify), but doesn't explicitly differentiate from 'mark_notification_as_read' which has a similar structure but targets notifications instead of watches.

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. It doesn't mention prerequisites (e.g., needing an existing watch), exclusions, or comparisons to similar tools like 'update_watching' which might also modify watch status. The description alone offers no contextual usage information.

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