Skip to main content
Glama

mark_all_as_read

Mark all articles in a FreshRSS stream as read to clear unread notifications. Specify a stream ID and optional timestamp to filter older articles.

Instructions

Mark all articles in a stream as read

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
streamIdYesStream ID (feed/123, user/-/label/FolderName, or user/-/state/com.google/reading-list)
olderThanNoOnly mark articles older than this Unix timestamp

Implementation Reference

  • The tool handler for 'mark_all_as_read' which calls the service layer.
    wrapTool('mark_all_as_read', async (args: z.infer<typeof markAllReadSchema>) => {
      await client.articles.markAllAsRead(args.streamId, args.olderThan);
      return textResult('Marked all articles in stream as read.');
    })
  • The actual service implementation that performs the API call for 'mark_all_as_read'.
    async markAllAsRead(streamId: string, olderThan?: number): Promise<void> {
      const body: Record<string, string> = { s: streamId };
      if (olderThan !== undefined && olderThan !== 0) {
        body.ts = String(olderThan * 1000000);
      }
      await this.http.post('/reader/api/0/mark-all-as-read', body);
    }
  • The registration of the 'mark_all_as_read' tool with the MCP server.
    server.registerTool(
      'mark_all_as_read',
      {
        description: 'Mark all articles in a stream as read',
        inputSchema: markAllReadSchema,
      },
      wrapTool('mark_all_as_read', async (args: z.infer<typeof markAllReadSchema>) => {
        await client.articles.markAllAsRead(args.streamId, args.olderThan);
        return textResult('Marked all articles in stream 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. It states the action (marking as read) but fails to disclose behavioral traits such as whether the operation is reversible (via 'mark_as_unread'), potential performance implications for large streams, or that it modifies article state.

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 no wasted words. It is appropriately front-loaded with the action and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple two-parameter structure with complete schema coverage, the description is minimally viable. However, it lacks mention of return values or success/failure behavior, which would be helpful given the absence of an output schema.

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 description coverage is 100%, establishing a baseline of 3. The description implies the streamId parameter by mentioning 'in a stream' but adds no semantic details beyond what the schema already provides for 'streamId' or 'olderThan'.

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 uses a specific verb ('Mark') and resource ('articles in a stream'), and distinguishes itself from sibling tool 'mark_as_read' by specifying 'all'. However, it does not explicitly clarify the distinction between bulk vs. individual marking 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?

The description provides no explicit guidance on when to use this tool versus 'mark_as_read' or other alternatives. While the word 'all' implies bulk usage, there are no explicit when/when-not conditions or prerequisites (e.g., warnings about large streams).

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/alysson-souza/freshrss-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server