Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Update RSS Feed

update_rss_feed
DestructiveIdempotent

Update an RSS feed's settings in AdaptlyPost by sending only the fields you want changed; use it to adjust targets, post mode, template, or filters without altering the feed URL.

Instructions

Change an RSS feed's settings; only the fields sent change, and the URL cannot change. The feed then posts as the member making the change, so they need the permission of the resulting post mode, plus posts.others when someone else set the feed up. Switching postMode to SCHEDULE or PUBLISH means later items go out without further confirmation, so confirm with the user first. Ids outside the workspace return 404. Needs the posts.draft 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": "update_rss_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRSS feed id from list_rss_feeds or create_rss_feed
nameNoName shown for the feed in AdaptlyPost. Defaults to the feed's title
targetsNoAccounts every new item is posted to, one entry per account
postModeNoDRAFT 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
contentModeNoTEMPLATE 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
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 updated 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.3/5.0
Behavior5/5

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

Goes well past the annotations (destructiveHint, idempotentHint, openWorldHint) with details an agent actually needs: patch semantics, an immutable URL, 404 for cross-workspace ids, credit spend for AI mode, and the consequential side effect that SCHEDULE/PUBLISH makes later items fire without further confirmation. The confirmation-warning is exactly the kind of behavior-level disclosure annotations cannot convey.

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?

Dense and front-loaded — patch semantics and the URL restriction come first, then permission and confirmation warnings. Every sentence carries information, but the permission requirements are split across two sentences ('permission of the resulting post mode' and 'Needs the posts.draft permission'), which reads slightly redundant.

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 15-parameter mutation tool this is complete: preconditions, permission model, side effects, error behavior (404), and a user-confirmation requirement are all covered, and an output schema exists so return values need no explanation.

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 real meaning on top: partial-update semantics, the fact that the feed URL is intentionally not a settable parameter, and the coupling of postMode to required permissions. It does not explain field-level interactions (e.g. publishDelayMinutes being required for SCHEDULE, which only the schema states), so it is not a full 5.

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?

States a specific verb and resource ('Change an RSS feed's settings') and immediately pins down the update semantics: only sent fields change and the URL is immutable. It is unambiguous about what the tool does, but it never names or contrasts the neighboring state tools (pause_rss_feed/resume_rss_feed) that also 'change' a feed.

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 usable context rather than exclusions: it explains the permission precondition (permission for the resulting post mode, plus posts.others when another member created the feed) and explicitly tells the agent to confirm with the user before switching postMode to SCHEDULE or PUBLISH. It does not route to a specific alternative tool, so it stops short of a 5.

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