Skip to main content
Glama
Nelson-PROIA

freebox-mcp

by Nelson-PROIA
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

put_downloads_feeds_feed_id_items_item_id

Modifies a specific download feed item's properties, such as status, title, or auto-download, to control RSS feed downloads on a Freebox.

Instructions

Returns the collection of all DownloadFeedItems for a given DownloadFeed

Error codes: feed_not_found, item_not_found, feed_is_recent, internal_error

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feed_idYes
item_idYes
idNoid
statusNoThe feed can have the following status — Values: `ready`: feed is up to date; `fetching`: feed is updating; `error`: there was an error trying to refresh this feed, see error
urlNoFeed URL
titleNoFeed title (extracted from the RSS)
descNoFeed description (extracted from the RSS)
image_urlNoFeed image URL (extracted from the RSS)
nb_readNoNumber of read items in the feed
nb_unreadNoNumber of unread items in the feed
auto_downloadNoIf set to true, the downloader will automatically download new items
fetch_tsNoLast time the feed was fetched — Unix timestamp (seconds since epoch).
pub_tsNoLast time the feed was published on remote server — Unix timestamp (seconds since epoch).
errorNoError code (same as used in Download or DownloadFile ).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / feed_id / type
      Previous value: -"integer"New value: +"string"
    • changedInput schema / properties / item_id / type
      Previous value: -"integer"New value: +"string"
  2. Changed23 schema fields changed
    • removedInput schema / properties / author
      Removed value: -{
-  "description": "item author",
-  "type": "string"
-}
    • addedInput schema / properties / auto_download
      Added value: +{
+  "description": "If set to true, the downloader will automatically download new items",
+  "type": "boolean"
+}
    • changedInput schema / properties / desc / description
      Previous value: -"item description"New value: +"Feed description (extracted from the RSS)"
    • removedInput schema / properties / enclosure_length
      Removed value: -{
-  "description": "enclosure size in bytes (if specified in RSS feed)",
-  "type": "integer"
-}
    • removedInput schema / properties / enclosure_type
      Removed value: -{
-  "description": "enclosure mime type (if specified in RSS feed)",
-  "type": "string"
-}
    • removedInput schema / properties / enclosure_url
      Removed value: -{
-  "description": "enclosure URL (if specified in RSS feed)",
-  "type": "string"
-}
    • addedInput schema / properties / error
      Added value: +{
+  "description": "Error code (same as used in Download or DownloadFile ).",
+  "type": "string"
+}
    • removedInput schema / properties / feed_id / description
      Removed value: -"id of the DownloadFeed"
    • removedInput schema / properties / feed_id__path
      Removed value: -{
-  "description": "id of the DownloadFeed containing the item (Path parameter)",
-  "type": "integer"
-}
    • changedInput schema / properties / fetch_ts / description
      Previous value: -"timestamp of the item creation — Unix timestamp (seconds since epoch)."New value: +"Last time the feed was fetched — Unix timestamp (seconds since epoch)."
    • addedInput schema / properties / image_url
      Added value: +{
+  "description": "Feed image URL (extracted from the RSS)",
+  "type": "string"
+}
    • removedInput schema / properties / is_downloaded
      Removed value: -{
-  "description": "mark downloaded items, automatically set to true when RSS item is downloaded",
-  "type": "boolean"
-}
    • removedInput schema / properties / is_read
      Removed value: -{
-  "description": "you can mark the item as read manually, or it is marked as read automatically when the item is downloaded",
-  "type": "boolean"
-}
    • removedInput schema / properties / item_id / description
      Removed value: -"id of the DownloadFeedItem to update"
    • removedInput schema / properties / link
      Removed value: -{
-  "description": "URL of the RSS feed attachment",
-  "type": "string"
-}
    • addedInput schema / properties / nb_read
      Added value: +{
+  "description": "Number of read items in the feed",
+  "type": "integer"
+}
    • addedInput schema / properties / nb_unread
      Added value: +{
+  "description": "Number of unread items in the feed",
+  "type": "integer"
+}
    • changedInput schema / properties / pub_ts / description
      Previous value: -"item publish timestamp — Unix timestamp (seconds since epoch)."New value: +"Last time the feed was published on remote server — Unix timestamp (seconds since epoch)."
    • addedInput schema / properties / status
      Added value: +{
+  "description": "The feed can have the following status — Values: `ready`: feed is up to date; `fetching`: feed is updating; `error`: there was an error trying to refresh this feed, see error",
+  "enum": [
+    "ready",
+    "fetching",
+    "error"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / title / description
      Previous value: -"item title"New value: +"Feed title (extracted from the RSS)"
    • addedInput schema / properties / url
      Added value: +{
+  "description": "Feed URL",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "feed_id__path",
-  "item_id"
-]New value: +[
+  "feed_id",
+  "item_id"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

D1.4/5.0
Behavior1/5

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

The description says 'Returns' implying a read operation, but PUT typically mutates. No annotations are provided, so the description carries full burden but fails to disclose mutation, permissions, or side effects. It directly contradicts the HTTP method implied by the tool name.

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

Conciseness2/5

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

The description is short but the single sentence is misleading about the tool's behavior. Error codes are listed but do not compensate for the incorrect purpose. The structure does not front-load a correct verb-resource combination.

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

Completeness1/5

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

The description fails to convey that this is an update tool (PUT) and incorrectly describes it as a return operation. Considering the complexity (14 parameters, output schema exists) and lack of annotations, the description is severely incomplete and inaccurate.

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 86%, so the input schema already describes parameters well. The description adds no additional parameter meaning beyond the schema, meeting baseline expectations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Returns the collection of all DownloadFeedItems for a given DownloadFeed,' which describes a GET operation, but the tool name starts with 'put_' indicating an update. This contradiction makes the purpose unclear and misleading.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'get_downloads_feeds_feed_id_items' (GET). The description does not clarify its role as an update operation, leaving the agent without usage context.

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