Skip to main content
Glama

mark_as_read

Mark articles as read in FreshRSS to manage your RSS feed reading progress and reduce unread counts.

Instructions

Mark one or more articles as read

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
articleIdsYesArticle IDs to mark

Implementation Reference

  • Tool registration for 'mark_as_read'.
    server.registerTool(
      'mark_as_read',
      {
        description: 'Mark one or more articles as read',
        inputSchema: markArticlesSchema,
      },
      wrapTool('mark_as_read', async (args: z.infer<typeof markArticlesSchema>) => {
        await client.articles.markAsRead(args.articleIds);
        return textResult(`Marked ${args.articleIds.length.toString()} article(s) as read.`);
      })
    );
  • Implementation of the 'markAsRead' method in the ArticleService, which is invoked by the handler.
    /**
     * Mark articles as read
     */
    async markAsRead(articleIds: string[]): Promise<void> {
      await this.http.post('/reader/api/0/edit-tag', {
        i: articleIds,
        a: 'user/-/state/com.google/read',
      });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Mark' implies a mutation, the description fails to disclose whether the operation is reversible (via 'mark_as_unread'), what the return value or success indicators are, or whether there are any side effects like triggering sync operations.

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 six words. It is appropriately front-loaded with the action and target, containing zero redundant or wasted language.

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 tool's simplicity (single parameter, no output schema), the description adequately covers the core functionality but leaves gaps. It could be improved by mentioning that this affects specific articles (differentiating from the 'all' variant) or noting that 'mark_as_unread' reverses this operation.

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 input schema has 100% description coverage ('Article IDs to mark'), establishing a baseline score of 3. The description adds minimal semantic value beyond the schema, though it reinforces the cardinality constraint ('one or more') which aligns with minItems: 1 in the schema.

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') with a clear state change ('as read'). It implicitly distinguishes from siblings like 'mark_all_as_read' (via 'one or more' vs. implied 'all') and 'mark_as_unread' (opposite state), though it doesn't explicitly name these alternatives.

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 on when to use this tool versus alternatives like 'mark_all_as_read' (for bulk operations) or 'mark_as_unread' (for the reverse action). It also doesn't indicate that article IDs should typically be sourced from 'list_articles' or similar tools.

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