Skip to main content
Glama
nulab

Backlog MCP Server

delete_watching

Delete a watch from an issue by providing the watch ID, stopping notifications for that issue.

Instructions

Deletes a watch from an issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
watchIdYesWatch ID to delete
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The handler function for the 'delete_watching' tool. It calls backlog.deletehWatchingListItem(watchId) with the provided watchId.
      handler: async ({ watchId }) => backlog.deletehWatchingListItem(watchId),
    };
  • Input schema for delete_watching: requires a watchId (number).
    const deleteWatchingSchema = buildToolSchema((t) => ({
      watchId: z
        .number()
        .describe(t('TOOL_DELETE_WATCHING_WATCH_ID', 'Watch ID to delete')),
    }));
  • Output schema (WatchingListItemSchema) for the tool response.
    export const WatchingListItemSchema = z.object({
      id: z.number(),
      resourceAlreadyRead: z.boolean(),
      note: z.string(),
      type: z.string(),
      issue: IssueSchema,
      lastContentUpdated: z.string(),
      created: z.string(),
      updated: z.string(),
    });
  • Import of deleteWatchingTool in the tools registry.
    import { deleteWatchingTool } from './deleteWatching.js';
  • Registration of deleteWatchingTool in the 'watching' toolset group.
    deleteWatchingTool(backlog, helper),
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action without elaborating on irreversibility, required permissions, or side effects. The word 'deletes' implies destruction but lacks specifics.

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?

A single sentence that is direct and efficient. No unnecessary information.

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?

The description is brief but misses critical context: no guidance on when to use versus other watching operations, no behavioral details on deletion consequences, and no output information. Given the potential destructive nature, more completeness is warranted.

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?

Schema covers all parameters with descriptions. Tool description does not add additional parameter semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (deletes) and the resource (watch from an issue). It differentiates from sibling tools like add_watching and update_watching, which perform distinct operations.

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 usage guidelines are provided. The description does not advise when to use this tool versus watching-related siblings like mark_watching_as_read, nor does it mention prerequisites or side effects. The agent must infer context solely from the name and description.

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