Skip to main content
Glama

list_unread_article_ids

Retrieve IDs of unread articles from FreshRSS to manage reading backlog and prioritize content consumption.

Instructions

List unread article IDs (Fever API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'list_unread_article_ids' which calls the Fever client to list unread IDs and returns the result as text.
    wrapTool('list_unread_article_ids', async () => {
      const ids = await client.fever.listUnreadIds();
      return textResult(ids.length === 0 ? 'No unread IDs.' : ids.join(','));
    })
  • Registration of the 'list_unread_article_ids' tool in the MCP server.
    server.registerTool(
      'list_unread_article_ids',
      {
        description: 'List unread article IDs (Fever API)',
        inputSchema: listIdsSchema,
      },
      wrapTool('list_unread_article_ids', async () => {
        const ids = await client.fever.listUnreadIds();
        return textResult(ids.length === 0 ? 'No unread IDs.' : ids.join(','));
      })
    );
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Fever API' hints at the protocol, the description lacks critical behavioral details: pagination behavior, rate limiting, whether the operation is read-only (implied but not stated), or what the return format looks like (array of integers, strings?).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at 6 words. Appropriately sized for a zero-parameter tool with no complex options. Front-loaded with the action verb. However, brevity borders on under-specification given the lack of output schema or annotations.

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?

Minimal but adequate for low complexity (zero params, simple list operation). However, with no output schema provided, the description should ideally specify the return structure (e.g., 'returns array of integer IDs'). Mentioning 'IDs' in the description partially addresses this but lacks format specificity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has zero parameters with 100% coverage (empty object). Per evaluation rules, zero-parameter tools baseline at 4. The description doesn't need to compensate for missing schema documentation, though it could have clarified if filters were available via other means.

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?

Clear verb 'List' and specific resource 'unread article IDs'. The 'Fever API' parenthetical adds context. However, it doesn't explicitly distinguish from sibling 'list_articles' (which likely returns full article objects vs. just IDs) or clarify the difference between 'unread' and 'starred' states relative to 'list_starred_article_ids'.

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 on when to use this versus 'list_articles' or 'list_starred_article_ids'. Doesn't mention prerequisites like authentication or that unread status is typically managed via 'mark_as_read'/'mark_as_unread' siblings. Zero guidance on selection criteria.

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