Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Preview RSS Feed

preview_rss_feed
Read-onlyIdempotent

Fetch an RSS or Atom feed without saving it, then preview its 5 newest posts rendered from a template before creating a feed. Use it to verify post text before anything is saved or published.

Instructions

Fetch an RSS or Atom feed without saving it and return its 5 newest items, each with text rendered from template, so the user can see what the posts would say before create_rss_feed. Fails with 400 when the URL is not a feed and 503 when it cannot be reached. Nothing is saved or posted. 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": {
      "url": "<url>"
    },
    "name": "preview_rss_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of an RSS or Atom feed
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
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 url, title, siteUrl and items: one { title, link, summary, publishedAt, imageUrl, text } per item, where text is the item rendered with template.

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 already declare read-only, idempotent, open-world, non-destructive, so the bar is lower; the description nonetheless adds the 5-item cap, explicit 400 (not a feed) and 503 (unreachable) failure modes, the posts.draft permission requirement, and a reaffirmation that nothing is saved or posted.

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?

Four tight sentences with the purpose and the 'without saving' constraint front-loaded. 'Nothing is saved or posted' slightly duplicates the opening clause and readOnlyHint, but the redundancy is cheap insurance.

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 3-parameter read tool, the description covers scope, item limit, error behavior, permission needed, and intended workflow; an output schema exists so return values need no further explanation.

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 coverage is 100% and the template placeholders are already fully documented in the schema, so the description only adds the detail that output text is template-rendered. Baseline 3 is correct when the schema carries parameter meaning.

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 — fetch an RSS/Atom feed without saving — plus the exact result shape (5 newest items, template-rendered text), and explicitly contrasts with create_rss_feed so the agent can separate preview from persistence.

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 a concrete when-to-use condition: 'so the user can see what the posts would say before create_rss_feed.' It names the sibling it precedes but offers no when-not guidance versus adjacent tools such as check_rss_feed.

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