Skip to main content
Glama
Sign In

Socialync

by io.github.JackVitick
OverviewDiscussionsAdmin

list_media

Read-only

List media (videos/images) the user already has in Socialync, available to schedule via the mediaId parameter of schedule_post_draft / publish_scheduled. Sources: uploads from the last 24 hours, active drafts, and pending scheduled posts. Use this when the user wants to post "the video I just uploaded" or attached a video file in chat (you cannot receive video files -- send them to socialync.io to upload it, then find it here). IMPORTANT: items marked unattached expire about 12 hours after upload unless scheduled -- schedule them promptly.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare this is a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is low, yet the description adds substantive behavior: the three media sources (24-hour uploads, active drafts, pending scheduled posts) and the ~12-hour expiry on unattached items. That expiry rule is exactly the kind of non-obvious trait an agent needs to act correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by source enumeration, usage triggers, and the expiry warning. Every sentence carries distinct, actionable information with no filler.

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 input parameters, no output schema, and annotations covering the safety profile, the description supplies everything else an agent needs: what is returned (media available to schedule), where it comes from, when to call it, and the time pressure on unattached items.

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 description references the mediaId parameter of sibling tools rather than this one, which is useful for chaining but not parameter semantics for this call itself.

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 media = videos/images already in Socialync) and immediately ties it to its downstream consumers via the mediaId parameter of schedule_post_draft / publish_scheduled. This distinguishes it cleanly from the sibling upload tools create_media_upload and finalize_media_upload.

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 names the triggering scenarios ('the video I just uploaded', or a video file attached in chat) and gives the fallback path (send the file to socialync.io to upload, then find it here). It also states a time-bound constraint: schedule unattached items promptly because they expire in ~12 hours.

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