Skip to main content
Glama
Sign In

flayr

by social.flayr
OverviewDiscussionsAdmin

List connected social accounts

list_connected_accounts
Read-onlyIdempotent

[read-only] The social accounts a brand can post to — the same set publish would use for that brandId: platform, handle, display name, health (healthy, needs_reauth, disconnected) and whether flayr can post there right now (postable; Reddit is paused because Reddit closed its API to third-party apps). Call this before publish to pick platforms, and tell the user to reconnect any account that is not healthy at flayr.social/connect. (Wraps GET /api/v2/accounts.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_connected_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoAn id from GET /api/v2/brands, or "personal". Omitted → the key's bound brand, else the owner's personal accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description rightly spends its budget on non-obvious behavior: the health state vocabulary, the postable flag, and the reason Reddit is paused. It also discloses the underlying endpoint. That is meaningful context beyond what any structured field carries.

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?

The purpose and the publish relationship are front-loaded, and the field enumeration is dense but useful. The Reddit parenthetical earns its place as an explanation of the postable field, though the sentence is long and the endpoint note is minor overhead.

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?

With no output schema, the description fully carries the return-value burden by naming every field and interpreting the health and postable values. Combined with the pre-publish guidance and reconnect URL, an agent has everything needed to call and act on this tool.

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?

The single brandId parameter is fully documented in the schema (100% coverage), and the description only references it in passing. It adds a light hint that brandId aligns with publish's scoping, but not enough to exceed the baseline when the schema already does the work.

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?

The description opens with a specific verb+resource ('The social accounts a brand can post to') and sharpens it by equating the set with what publish uses, then enumerates the returned fields. This clearly separates it from siblings like list_brands or list_publish_actions without needing the 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?

It states a concrete when-to-use ('Call this before publish to pick platforms') and a follow-up action ('tell the user to reconnect any account that is not healthy'). It stops short of naming a when-not-to-use or an explicit alternative tool, so it lands at 4 rather than 5.

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

All flayr 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