Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

List RSS Feed Items

list_rss_feed_items
Read-onlyIdempotent

Lists an RSS feed's items newest first with statuses (posted, filtered, skipped, failed) to show why each article was or was not published.

Instructions

List the items an RSS feed has seen, newest first, leaving out the ones already in the feed when it was added. Each item has a status: PROCESSING, POSTED (postId links it to its post, for get_post), FILTERED (keyword rules), SKIPPED (published more than 14 days before the feed was added) or FAILED (error says why). Returns { items } with id, createdAt, title, link, publishedAt, status, postId and error per item. Use it to answer why an article was or was not posted. Needs the posts.read permission.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "list_rss_feed_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRSS feed id from list_rss_feeds or create_rss_feed
limitNoItems to return, newest first (default 20)
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with items: one { id, createdAt, title, link, publishedAt, status, postId, error } per item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior beyond them: the five-value status semantics, the 14-day SKIPPED rule, keyword-based FILTERED, the exclusion of pre-existing items, and the posts.read permission requirement. For a read tool this is unusually complete disclosure.

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?

Front-loaded with the scope constraint, then a status glossary, then return shape and permission. Dense but every sentence carries information. The parenthetical-heavy middle sentence is slightly harder to scan than a list would be, but nothing is wasted.

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

Completeness5/5

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

A three-parameter read tool with an output schema, and the description still supplies the status semantics an agent needs in order to interpret results, plus the auth prerequisite. Nothing required to call it or read its output correctly is missing.

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 100%, so id, limit, and workspaceId are already fully documented including the workspace-id consistency rule. The description adds no parameter-level detail (e.g. no mention of limit or the default of 20), so it matches the baseline rather than exceeding it.

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?

States a specific verb and resource ('List the items an RSS feed has seen') plus a precise scope qualifier: newest first, excluding items that predate the feed's creation. That scope distinguishes it from get_rss_feed and list_rss_feeds, and the status taxonomy further pins down exactly what a row represents.

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

Usage Guidelines4/5

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

Gives an explicit use case ('Use it to answer why an article was or was not posted') and routes the agent onward to get_post via postId. It does not name an alternative to use instead when the question is about the feed itself rather than its items, so it stops short of full when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools