Postly MCP

Upload Media Batch

postly_upload_media_batch

Idempotent

Uploads up to 50 files with bounded concurrency and a 30-second overall deadline. Returns completed, failed, not_started, or unknown for every item with its stable idempotency key. Unknown uploads may still complete; reconcile stored media or retry with the same key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`media_uploads`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`failed`	No
`message`	No
`results`	No
`unknown`	No
`completed`	No
`elapsed_ms`	No
`not_started`	No
`all_succeeded`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 17, 2026

addedOutput schema / properties / elapsed_ms
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / not_started

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / unknown

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

AddedSep 16, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing bounded concurrency, a 30-second overall deadline, four possible per-item outcomes, and the open-world nuance that unknown uploads may still complete with reconciliation/retry guidance. This is exactly the behavioral context an agent needs, and it is consistent with the openWorldHint and idempotentHint 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?

Three dense sentences, each earning its place: the action/constraint, the result vocabulary, and the failure-handling caveat. Front-loaded and free of 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?

For a batch upload tool with an output schema, this covers the important operational details: batch limit, deadline, concurrency, outcome states, and retry behavior. It falls slightly short of fully complete because it leaves the choice of single vs batch upload and the url/data/file parameter trade-offs to inference or the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Context reports 0% schema description coverage, so the description carries the burden of explaining the media_uploads payload; it does not mention the url/data/file source alternatives or the file_name requirement for base64 input. It does add retry semantics for the idempotency_key, which is partial but insufficient compensation for the low coverage.

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 action and resource: uploading media, bounded to 50 files, with per-item status reporting. The batch scope is evident from the name/title and 'up to 50 files', which separates it from the single-file sibling postly_upload_media without needing to inspect either schema.

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?

The batching constraint ('up to 50 files') and deadline imply that this tool is for bulk media uploads, but the description never explicitly says when to prefer it over postly_upload_media or gives a when-not-to-use condition. Usage is inferable rather than stated.

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?