Feedlio

Disconnect a social account from Feedlio

disconnect_social_account

DestructiveIdempotent

Disconnect a social account (uid from list_social_accounts) from Feedlio. This cannot be undone through MCP — confirm with the user first, naming the account and saying what happens to its posts. Feedlio forgets the account's sign-in and removes the account from every post in Feedlio, with its post analytics: scheduled posts that were only for this account are deleted, posts that also go to other accounts still publish there. Posts already published stay live on the platform itself; drafts are not changed. To use the account again, the user reconnects it (get_connect_platform_link).

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": {
      "social_account_uid": "<social_account_uid>"
    },
    "name": "disconnect_social_account"
  }
}

Input Schema

Name	Required	Description	Default
`social_account_uid`	Yes	uid from list_social_accounts

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes well beyond them: it details exactly what is removed (sign-in, account from every post, its post analytics), the differential outcome for account-only scheduled posts vs. multi-account posts, that published posts stay live on the platform, and that drafts are untouched.

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-loads the action and the confirmation requirement, then sequences consequences logically. Dense but nearly every clause carries real decision value; the multi-clause middle sentence could be split for readability, which keeps it just short of a 5.

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 one-parameter destructive tool with no output schema, the description supplies everything an agent needs: irreversibility, confirmation protocol, per-post outcome matrix, and the reconnect path. No meaningful gap remains.

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 single parameter is already documented as 'uid from list_social_accounts'; the description repeats that origin but adds no format, validation, or sourcing detail beyond the schema. Baseline 3 applies since the schema carries the parameter burden.

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 (disconnect a social account from Feedlio) and immediately ties the required uid to list_social_accounts, which separates it cleanly from sibling tools like get_connect_platform_link or delete_post.

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 requires user confirmation naming the account before calling, and names the concrete alternative path for reversing course ('the user reconnects it (get_connect_platform_link)'). When-to-use, when-to-warn, and where-else-to-go are all present.

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

All Feedlio tools Inspect

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

Need Help?