Skip to main content
Glama
Sign In

Socialync

by io.github.JackVitick
OverviewDiscussionsAdmin

list_audiences

Read-only

List the user's saved audiences. An audience is a named group of connected accounts the user built in Socialync (e.g. "Core 12"), reusable as a posting target. Returns each audience with id, name, scope, member count, and the members (platform + account label). Pass an audience id as the audienceId param on create_post_draft / schedule_post_draft / publish_now / publish_scheduled to post to that group instead of listing platforms; anything the audience cannot reach on the chosen profile is reported back in skippedMembers.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, not open-world), so the description adds the return field list and the skippedMembers behavior for downstream posting. Useful context beyond structured data, but no mention of pagination, ordering, or empty-result behavior.

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?

Purpose is front-loaded in the first sentence and each following sentence adds distinct value (definition, return shape, downstream usage). It is slightly dense but has no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the return-value burden and does so by enumerating id, name, scope, member count, and members. Only pagination/limit behavior and the empty-audience case are left unstated.

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 tool takes zero parameters, so the baseline is 4. The only parameter discussed (audienceId) belongs to sibling tools, not this one, so there is no parameter semantics to clarify here.

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 ("List the user's saved audiences") and then defines the domain object an audience is, including a concrete example. This clearly distinguishes it from account-level siblings like list_connections.

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 routes the agent forward: pass an audience id as audienceId on create_post_draft / schedule_post_draft / publish_now / publish_scheduled instead of listing platforms. That is clear conditional context and names the alternatives, though there is no explicit "when not to use this" statement.

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

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