Skip to main content
Glama

Generate social posts from an RSS / blog item

generate_posts_from_rss_item

Runs the same RSS → social posts flow as the Flomixy app for an article already in a connected feed: one AI-written caption per target network (with the article link and the feed image, same as the app's "AI variants"). Never publishes directly: without scheduledAt the posts stay DRAFTS; with scheduledAt they are scheduled but still wait for human approval. Pick times with get_best_times / get_next_free_slot. Must be at least 10 minutes from now, otherwise SCHEDULED_TOO_SOON (not retryable; the error names the earliest allowed time). Get feedId/itemId from list_rss_feeds and accountId from list_accounts. Each network uses one AI caption unit; networks that cannot be generated (duplicate caption, account not owned by the feed's brand, or the article is already posted/scheduled/drafted on that very account: reason ALREADY_POSTED with existingPostId and existingStatus) come back in skipped, not as an error; no AI unit is spent for them. Use force only if the user wants another post anyway. Requires scope POSTS_WRITE.

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": {
      "feedId": "<feedId>",
      "targets": "<targets>"
    },
    "name": "generate_posts_from_rss_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoSet true ONLY when the user explicitly wants another post for an article that already has one on the account. Default false: such networks come back in `skipped` with reason ALREADY_POSTED.
feedIdYesFeed id from list_rss_feeds.
itemIdNoItem id from list_rss_feeds. Exactly one of itemId / itemUrl.
itemUrlNoLink of an article already in the feed (e.g. the blog URL). Exactly one of itemId / itemUrl.
targetsYesOne post is generated per entry.
languageNoCaption language, default "en".
approverIdNoWorkspace member who should review the posts (list_approvers).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so thoroughly: drafts unless scheduledAt is set, scheduling still requires human approval, a 10-minute minimum with the non-retryable SCHEDULED_TOO_SOON error and earliest-allowed time, per-network skipped results with ALREADY_POSTED/existingPostId/existingStatus, AI caption unit consumption, and required POSTS_WRITE scope.

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 core action and the never-publishes constraint, then prerequisites and error conditions. It is dense and semicolon-heavy in a single block, but nearly every clause carries operational value; a small amount of restructuring into bullets would improve scanability.

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 7-parameter generation tool with no output schema and no annotations, the description covers preconditions, side effects, cost model, permission scope, and failure/skip semantics — everything an agent needs to invoke it correctly and interpret partial results.

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 genuine meaning beyond the schema: it explains scheduledAt's draft-vs-scheduled consequence, force's ALREADY_POSTED trade-off, and the per-target `skipped` outcome for accounts not owned by the feed's brand. Only language/approverId/itemId-vs-itemUrl get no extra narrative.

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 — generates one AI-written social post per target network from an RSS feed item, mirroring the app's 'AI variants' — and implicitly separates itself from create_post/create_draft_post by noting it never publishes directly. An agent can immediately tell what it produces.

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: obtain feedId/itemId from list_rss_feeds, accountId from list_accounts, and pick times with get_best_times / get_next_free_slot. It also constrains when to use `force` ('only if the user wants another post anyway') and states the alternative outcome (skipped) when not used.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources