Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Create RSS Feed

create_rss_feed
Destructive

Connect an RSS or Atom feed to automatically turn new items into social posts across selected accounts, with draft, scheduled, or immediate publishing options.

Instructions

Connect an RSS or Atom feed so each new item becomes a post on the target accounts. The feed is fetched and every item already in it is recorded, so only items that appear later are posted; postLatestItem also posts the newest one on the first check. The feed is then checked every checkIntervalMinutes and posts as the member who saved it, as a draft, a scheduled post or straight away (postMode). With postMode SCHEDULE or PUBLISH, posts go out on the user's accounts without further confirmation, so confirm the feed, the accounts, the mode and the text with the user first. Try preview_rss_feed first to show what the posts will say. Fails with 400 for invalid settings, a URL that is not a feed, a feed already connected or the 20-feed workspace limit, and 503 when the feed cannot be reached. Needs posts.draft, plus the permission of the post mode.

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": {
      "url": "<url>",
      "targets": "<targets>",
      "postMode": "<postMode>",
      "contentMode": "<contentMode>"
    },
    "name": "create_rss_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of an RSS or Atom feed
nameNoName shown for the feed in AdaptlyPost. Defaults to the feed's title
targetsYesAccounts every new item is posted to, one entry per account
postModeYesDRAFT creates a draft and needs posts.draft; SCHEDULE schedules the post publishDelayMinutes after the item is found and needs posts.schedule; PUBLISH publishes it right away and needs posts.publish
templateNoPost text with {title}, {link}, {description}, {author} and {feed} (default "{title}\n\n{link}"). The description, then the title, is shortened to fit each platform; the link is never cut
contentModeYesTEMPLATE fills template; AI writes one caption per platform from the article, appends the link, spends 1 AI credit per platform per item and needs ai.generate
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
includeImageNoAttach the item's image, or the article's preview image (default true)
aiInstructionsNoExtra instructions for AI captions, such as tone or hashtags. Used when contentMode is AI
postLatestItemNoAlso post the newest item on the first check (default false)
excludeKeywordsNoSkip items whose title or summary contains one of these
includeKeywordsNoPost only items whose title or summary contains one of these
maxPostsPerCheckNoNew items posted per check (default 3). New items are posted oldest first; the rest wait for the next check
twitterKeepLinksNoKeep links in X posts clickable (default false). Lifetime-deal plans only; each X post with a link then costs more credits. Without it, links on X go out as plain text
publishDelayMinutesNoMinutes between finding an item and its post going out. Required when postMode is SCHEDULE
checkIntervalMinutesNoMinutes between checks of the feed (default 60)

Output Schema

NameRequiredDescriptionDefault
resultYesThe new feed. The RSS feed: id, userId (the member it posts as, whoever last saved it), name, url, siteUrl, status (ACTIVE or PAUSED), pauseReason, lastError, postMode, publishDelayMinutes, contentMode, template, aiInstructions, includeImage, twitterKeepLinks, includeKeywords, excludeKeywords, maxPostsPerCheck, checkIntervalMinutes, targets, nextCheckAt, lastCheckedAt, lastPostedAt, createdAt and updatedAt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.6/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: existing items are recorded at connect time so only later items post, checks recur on checkIntervalMinutes, posts are authored as the saving member, and posts publish without further confirmation in SCHEDULE/PUBLISH. Also discloses 400 and 503 failure conditions, the 20-feed workspace limit, and required scopes. The main omission is what the create response returns, which the output schema likely covers.

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 what the tool does, then behavior, then the safety warning, then failure modes and permissions. Dense and mostly waste-free, though the confirmation and permissions sentences could be tightened slightly.

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?

For a 16-parameter, destructive, open-world tool with an output schema, the description covers setup semantics, side effects, permissions, limits, error codes and a preview alternative. An agent has everything needed to call it correctly and safely.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds lifecycle meaning: postLatestItem's special first-check behavior, the per-check cadence tied to checkIntervalMinutes, and the confirmation burden attached to postMode. It explains how settings interact rather than restating types.

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?

Opens with a specific verb and resource ("Connect an RSS or Atom feed") and states the effect on the target accounts. It is clearly separable from siblings like preview_rss_feed and check_rss_feed, which it names or implies through distinct behavior.

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

Usage Guidelines5/5

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

Explicitly routes the agent: "Try preview_rss_feed first to show what the posts will say" and mandates confirming feed, accounts, mode and text with the user before SCHEDULE or PUBLISH. When-not guidance is also present via the failure conditions.

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