Postly MCP

List Media

postly_list_media

Read-onlyIdempotent

Lists durable stored media, or recovers one upload by idempotency_key. Recovery reports completed only when storage confirms the file; unknown uploads may still complete. Requires media.read.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of files to return.
`offset`	No	Number of stored files to skip.
`idempotency_key`	No	Recover a specific upload using its returned key instead of listing files. An unknown result may still be in progress; retry uploads only with this same key.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`files`	No
`status`	No
`message`	No
`pagination`	No
`idempotency_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 17, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Recover a specific upload using its returned key instead of listing files. An unknown result may still be in progress; retry uploads only with this same key.",
+  "type": "string"
+}

addedOutput schema / properties / idempotency_key
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / status
```
Added value: +{
+  "type": "string"
+}
```

AddedSep 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, non-destructive), the description adds two high-value disclosures: the auth prerequisite ('Requires media.read') and the consistency behavior ('Recovery reports completed only when storage confirms the file; unknown uploads may still complete'). These are genuine behavioral traits an agent needs and are not present in the annotations or schema.

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 dense sentences with zero filler: the first front-loads the core dual purpose, the second adds the critical consistency caveat and auth note. Every sentence earns its place.

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 an output schema present, return values need no explanation, and annotations cover the safety profile. The description fills the remaining gaps — auth, consistency, and mode semantics — leaving nothing essential missing for correct invocation. Minor omissions like list ordering are immaterial for a tool with this complexity.

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 description coverage is 100%, so the schema fully documents limit, offset, and idempotency_key. The description mentions idempotency_key functionally but adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('Lists durable stored media, or recovers one upload by idempotency_key'), and it clearly distinguishes this from sibling list tools (media vs posts/accounts/workspaces) and from the upload tools (recovery is not uploading). The dual-mode scope is stated unambiguously in the first sentence.

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?

The description gives clear mode-selection context: use listing when you want stored files, use recovery when you hold an idempotency_key. It also warns about the in-progress semantics of recovery ('unknown uploads may still complete'). However, it never names sibling alternatives or states when-not-to-use (e.g., pointing to postly_upload_media for uploading), leaving the alternative routing implicit.

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

All Postly MCP tools Inspect

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

Need Help?