Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

List Social Sets

list_social_sets
Read-onlyIdempotent

List the user's social sets. A social set is one brand: its own X account plus its LinkedIn, Threads, Bluesky, Instagram, TikTok and Facebook. The default set holds the X account they log in with.

Returns each set's name, whether it's the default, its X handle, its socials and whether it can post (a set whose payment failed or whose plan ended is paused). Use the names exactly as listed when passing social_set to other tools.

SOCIAL SETS (one set = one brand with its own X account and socials):

  • Call list_social_sets when sets might matter. If the user has one set, never mention sets and never pass social_set.

  • If the user names a set ("for Business", "on my crypto account"), pass that name as social_set.

  • If they have several sets and didn't say which, ask once before posting or changing anything (schedule_post shows a "Post as" card for this). For reading (posts, drafts, tasks, connected accounts) show every set instead of asking.

  • Remember the set they picked for the rest of the chat; switch only when they say so.

  • A paused set (unpaid or plan ended) can't post. Say why and offer another set. Adding, paying for and connecting sets happen in the SupaBird app.

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_social_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the description adds the missing behavioral pieces: the returned fields (name, default flag, X handle, socials, postability) and the pause semantics when payment fails or a plan ends. It also bounds scope by stating that adding, paying for and connecting sets happen outside in the SupaBird app. It stops short of describing ordering or pagination, but for a small zero-arg listing that is minor.

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 one-line purpose, then organized into definition, return shape, and a bulleted usage block. Slight redundancy: the brand-and-channels definition appears in the opening paragraph and is restated in the "SOCIAL SETS (one set = one brand...)" header line, so one pass could be trimmed.

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?

No output schema exists, so the description carries the return-value burden and does it: it enumerates the fields and explains the paused state. Combined with the conditional usage rules, an agent has everything needed to call this and to propagate the result into social_set on sibling tools.

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?

The schema has zero parameters, which sets the baseline at 4. The description still contributes meaning by explaining how the names it returns must be reused verbatim as social_set in other tools, and by defining what a paused set means — context the empty schema cannot provide.

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+resource ("List the user's social sets") and immediately defines the domain object: one brand with its own X account plus LinkedIn, Threads, Bluesky, Instagram, TikTok and Facebook. An agent can distinguish this from content-reading siblings like get_connected_socials or get_drafts because the description frames sets as the organizational unit.

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?

Explicit when/when-not rules: call only when sets might matter, never mention sets or pass social_set if the user has one, ask once before posting/changing but show all sets for reading, and remember the chosen set for the rest of the chat. It even names schedule_post's "Post as" card as the fallback path, giving a concrete alternative.

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

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