Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

list_media

List media library files and return reusable IDs for post_image or post_video, letting you attach existing images, videos, or documents without re-uploading. Filter by type, filename, or limit.

Instructions

List files in the media library. Returns IDs you can reuse in post_image or post_video without re-uploading.

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
typeNoFilter by media type
limitNoMax results (default 20)
searchNoSearch by filename

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavior burden; it does disclose the meaningful trait that returned IDs can be reused without re-uploading, which the schema does not convey. It omits permission requirements, pagination/truncation behavior beyond the schema's limit, and ordering, so it adds some but not rich behavioral context.

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?

Two short sentences, front-loaded with the action and immediately followed by the useful payoff (reusable IDs). No filler.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-optional-parameter list tool without an output schema, saying it returns IDs covers the main return question, but empty-result behavior, ordering and pagination are unaddressed, leaving mild gaps.

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?

Schema coverage is 100%: type enum, limit bounds/default and search are fully documented in the schema. The description adds no filter semantics (e.g. how search matches, whether type omits documents), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List files in the media library") and ties the result to concrete downstream tools (post_image, post_video), so the agent can tell it is a read/lookup tool distinct from post_* or delete_media. It stops short of naming the sibling it is not, e.g. delete_media, so it is not a full 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'you can reuse in post_image or post_video without re-uploading', which suggests fetching IDs before publishing, but there is no explicit when-to-use vs when-not guidance or statement of alternatives.

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