list_connected_accountsList social accounts connected to the Fuxux workspace. Use an account's id in create_post targets to pick which account posts when a platform has more than one.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| accounts | Yes | ||
| workspace_name | No | ||
| is_team_workspace | No |
Changes observed during successful MCP inspections.
Output schema / properties / accounts / items / properties / platform_username / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / accounts / items / properties / platform_username / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / accounts / items / properties / status / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / accounts / items / properties / status / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / accounts / items / properties / via_reminder / anyOfRemoved value: -[
- {
- "type": "boolean"
- },
- {
- "type": "null"
- }
-]Output schema / properties / accounts / items / properties / via_reminder / typeAdded value: +[
+ "boolean",
+ "null"
+]Output schema / properties / is_team_workspace / anyOfRemoved value: -[
- {
- "type": "boolean"
- },
- {
- "type": "null"
- }
-]Output schema / properties / is_team_workspace / typeAdded value: +[
+ "boolean",
+ "null"
+]Output schema / properties / workspace_name / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / workspace_name / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / accounts / items / properties / created_atRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
-}Output schema / properties / accounts / items / properties / id / descriptionAdded value: +"Use as account_id in create_post targets"Output schema / properties / accounts / items / properties / platform_avatar_urlRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
-}Output schema / properties / accounts / items / properties / scopesRemoved value: -{
- "anyOf": [
- {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
- ]
-}Output schema / properties / accounts / items / properties / token_expires_atRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
-}Output schema / properties / accounts / items / properties / via_reminder / descriptionAdded value: +"True for a reminder-only entry: Fuxux reminds the user to post, it does not publish"Output schema / properties / workspace_idRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
-}Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": {},
+ "properties": {
+ "accounts": {
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "created_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "type": "string"
+ },
+ "platform": {
+ "type": "string"
+ },
+ "platform_avatar_url": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "platform_username": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "scopes": {
+ "anyOf": [
+ {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "status": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "connected | expired"
+ },
+ "token_expires_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "via_reminder": {
+ "anyOf": [
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "platform"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "is_team_workspace": {
+ "anyOf": [
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "workspace_id": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "workspace_name": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "accounts"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds workspace scoping (only accounts connected to this workspace) and the key semantic trait that the returned ids are stable references consumed by create_post — meaningful beyond the annotations. It says nothing about what happens when no accounts exist, which is the only real gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action and resource, second sentence devoted entirely to how to use the output. Nothing is padded and nothing is repeated from the schema or annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A read-only, no-param, output-schema-backed list tool — the return shape is documented elsewhere, so the description need not restate it. It covers purpose, scope and downstream id usage. Minor gap: no mention of ordering or the empty-accounts case.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-arg tool is 4. The description correctly implies no filtering input is accepted — the workspace itself scopes the result.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb + resource: 'List social accounts connected to the Fuxux workspace.' The resource (accounts) is inherently distinct from the post-centric siblings (list_posts, create_post, get_post), though the description never names or contrasts an alternative explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives concrete downstream usage rather than an abstract 'when to use': feed the returned account id into create_post targets to disambiguate posting when a platform has multiple accounts. This is a clear context signal an agent can act on. It doesn't state exclusions, but no sibling offers a competing way to enumerate accounts, so little is left ambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.