Skip to main content
Glama

list_starred_article_ids

Retrieve IDs of saved or starred articles from your FreshRSS feed reader for further management or processing.

Instructions

List starred/saved article IDs (Fever API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for 'list_starred_article_ids' which fetches saved IDs from the Fever API client.
    wrapTool('list_starred_article_ids', async () => {
      const ids = await client.fever.listSavedIds();
      return textResult(ids.length === 0 ? 'No starred IDs.' : ids.join(','));
    })
  • Registration of the 'list_starred_article_ids' tool in the MCP server.
    server.registerTool(
      'list_starred_article_ids',
      {
        description: 'List starred/saved article IDs (Fever API)',
        inputSchema: listIdsSchema,
      },
      wrapTool('list_starred_article_ids', async () => {
        const ids = await client.fever.listSavedIds();
        return textResult(ids.length === 0 ? 'No starred 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 'List' implies read-only, it does not confirm safety, disclose pagination behavior, rate limits, or return format (e.g., array of integers). 'Fever API' hint is the only behavioral clue.

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?

Single efficient sentence of 6 words. Front-loaded with action and resource. No redundant or filler text; every word earns its place for this simple retrieval tool.

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 zero parameters and simple purpose, description adequately identifies the return concept ('IDs'). However, with no output schema and no annotations, it omits return type structure (array format) and behavioral constraints that would help invocation.

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, establishing baseline 4. Description appropriately does not invent parameter semantics where none exist.

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?

Specific verb 'List' plus exact resource 'starred/saved article IDs' clearly distinguishes from sibling 'list_articles' (full objects) and 'list_unread_article_ids' (different filter). The 'Fever API' parenthetical adds useful protocol context.

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' (which likely returns full article metadata) or how it relates to mutation siblings 'star_articles'/'unstar_articles'. Lacks explicit when-to-use 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