Skip to main content
Glama
Sign In

Postemi: Social Media Scheduler

by com.postemi
OverviewDiscussionsAdmin

list_upload_link_files

Read-only

The files the user dropped on an upload link from create_upload_link, with the hosted path to attach to a post.

Call this after the user tells you the upload is done, with the uploadLinkId you were given. Pass each file's PATH - not its id - as the create_post attachment.

If status is "empty", nothing has arrived yet: tell the user you do not see the file, ask them to check the page showed "uploaded", and call again when they confirm. Do not search the media library instead, and do not ask the user for a path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uploadLinkId": "<uploadLinkId>"
    },
    "name": "list_upload_link_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
uploadLinkIdYesThe uploadLinkId returned by create_upload_link.

Output Schema

NameRequiredDescriptionDefault
errorNo
outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, it discloses the meaningful 'empty' result state and the exact recovery workflow. It also warns that the agent must use the file path rather than the file id when passing attachments to create_post, which is important behavior not captured by annotations.

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?

The definition is front-loaded with what the tool returns and then adds only actionable workflow guidance. Every sentence contributes either selection guidance, parameter usage, or empty-state handling.

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?

For a simple read-only listing tool with an output schema, the description covers the essential call timing, identifier source, attachment-path usage, and empty-state recovery. Nothing material is missing for correct invocation.

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% for the single uploadLinkId parameter, and the schema already says it comes from create_upload_link. The description reinforces the same meaning but does not add format or validation details beyond the schema, so the baseline 3 is appropriate.

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?

It states a specific verb and resource: list the files a user dropped on an upload link created by create_upload_link. It also distinguishes the result from other workflows by saying the hosted path is what attaches to a post, which helps separate it from create_post and upload_media_from_url.

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?

The description gives explicit timing ('after the user tells you the upload is done'), the required identifier source, and clear anti-patterns: do not search the media library and do not ask the user for a path. It also prescribes behavior for the 'empty' status, making the when-and-what-to-do guidance unusually complete.

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

All Postemi: Social Media Scheduler 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