Skip to main content
Glama

unsubscribe_feed

Remove an RSS feed from your Tiny Tiny RSS subscriptions by specifying the feed ID to stop receiving updates.

Instructions

取消订阅指定的 RSS 源

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feed_idYes要取消订阅的源 ID

Implementation Reference

  • The tool handler for "unsubscribe_feed" which calls the client's unsubscribeFeed method.
    async ({ feed_id }) => {
      try {
        await client.unsubscribeFeed(feed_id);
        return { content: [{ type: "text" as const, text: "取消订阅成功" }] };
      } catch (e: unknown) {
        return {
          content: [{ type: "text" as const, text: `取消订阅失败: ${(e as Error).message}` }],
  • The registration of the "unsubscribe_feed" tool with its input schema.
    server.tool(
      "unsubscribe_feed",
      "取消订阅指定的 RSS 源",
      {
        feed_id: z.number().describe("要取消订阅的源 ID"),
      },
  • The actual client implementation that performs the API request to unsubscribe from a feed.
    async unsubscribeFeed(feedId: number): Promise<{ status: string }> {
      return this.request("unsubscribeFeed", { feed_id: feedId });
    }
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 of behavioral disclosure. It states the action ('取消订阅') but doesn't describe effects (e.g., whether it's reversible, if it requires specific permissions, or what happens to associated data like articles). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 in Chinese that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the tool's complexity as a mutation operation, lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, error conditions, or return values, which are crucial for an agent to use it correctly.

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 schema description coverage is 100%, with the single parameter 'feed_id' documented as '要取消订阅的源 ID' (ID of the feed to unsubscribe). The description doesn't add any meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 clearly states the action ('取消订阅' meaning 'unsubscribe') and the resource ('指定的 RSS 源' meaning 'specified RSS feed'), making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'subscribe_feed' or 'get_feeds', but the verb clearly indicates a write operation versus read 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 guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing subscription), exclusions, or comparisons to sibling tools like 'subscribe_feed' or 'get_feeds', leaving usage context implied rather than explicit.

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/aooiuu/ttrss-mcp'

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