Skip to main content
Glama
Sign In

Feedlio

by io.feedlio.mcp
OverviewDiscussionsAdmin

Get one post

get_post
Read-onlyIdempotent

Get one post or draft with everything about it: text, media, first comment, the time it is scheduled for, the saved platform settings (settings: youtube, tiktok, pinterest, google_business_profile button and button_url, with the same field names create_post takes), and for each account whether it is pending, published or failed, when it was published, a link to the live post where the platform provides one (live_url, e.g. the Google post link), and the failure reason. Use it after create_post to check the result, or before editing. post_uid comes from list_posts or create_post. Timestamps are UTC.

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": {
      "post_uid": "<post_uid>"
    },
    "name": "get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_uidYesuid from list_posts or create_post
workspace_uidNouid of the workspace the post belongs to; omit for the default workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it spells out the per-account result states (pending, published, failed), the presence of live_url when the platform supplies one, the failure reason, and that timestamps are UTC. No auth or rate-limit notes, which keeps it off a 5.

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, then a dense payoff sentence, then short operational sentences. The parenthetical listing every settings field is long but earns its place because no output schema exists to carry the return shape. Slightly dense but no filler.

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?

There is no output schema, so the description carries the entire burden of describing the return value, and it does so thoroughly: core content, scheduling, platform-specific settings, per-account status, live link, and failure reason. Combined with annotations covering the safety profile, an agent has everything needed to call this correctly.

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% and both parameters are documented there, so the baseline applies. The description restates the post_uid provenance already present in the schema and says nothing about workspace_uid (e.g. that omitting it falls back to the default workspace), adding no meaning beyond the structured fields.

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 ("Get one post or draft") and immediately distinguishes the scope by enumerating what is returned: text, media, first comment, schedule time, platform settings, and per-account publish status. An agent can separate this from list_posts, create_post, and update_post without opening any schema.

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 concrete usage contexts ("after create_post to check the result, or before editing") and names where post_uid originates (list_posts or create_post), which effectively routes the agent away from this tool for enumeration. It stops short of an explicit "do not use to list multiple posts" statement, so it is clear context rather than full when/when-not coverage.

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

All Feedlio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources