Postfjord

Get media

postfjord_get_media

Read-only

One file in the media library by id, as postfjord_list_media shows it, and for a picture that is ready previews: a link (valid one hour) with width and height for each stored shape (original, 1x1, 4x5, 16x9, 9x16), so you can see how a crop would look before choosing a shape. A channel's own crop (a focus, a zoom, or whole) shows in postfjord_preview_post. Use it after postfjord_upload_media to see when the file is ready: a picture takes a few seconds, a video up to a minute.

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": {
      "mediaId": "<mediaId>"
    },
    "name": "postfjord_get_media"
  }
}

Input Schema

Name	Required	Description	Default
`mediaId`	Yes	A media id, from postfjord_list_media or postfjord_upload_media.

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`name`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / mediaId / description

Added value: +"A media id, from postfjord_list_media or postfjord_upload_media."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "kind": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered; the description adds genuinely new behavior: the returned link expires after one hour, and readiness lag differs by type (seconds for pictures, up to a minute for video). It does not mention pagination or rate limits, but for a single-resource read those are minor.

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

Conciseness3/5

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

The information is dense and mostly front-loaded, but the opening clause 'as postfjord_list_media shows it' is awkward and the shape list (original, 1x1, 4x5, 16x9, 9x16) bloats a sentence that could be summarized. Nothing is outright filler, yet the prose reads as run-on rather than structured.

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 one-parameter read with an output schema, the description covers the important non-obvious facts: what the preview payload contains, link expiry, and how long readiness takes after upload. An agent can call it correctly and interpret the result; only multi-id behavior and failure modes are unaddressed.

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% and the single mediaId parameter already carries a pattern and a description pointing at postfjord_list_media / postfjord_upload_media. The description restates 'by id' without adding format or sourcing detail 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?

States a specific verb and resource ('One file in the media library by id') and immediately scopes what is returned: a one-hour link plus width/height per stored shape. It also names the sibling tools that cover the adjacent cases (postfjord_list_media for listing, postfjord_preview_post for channel crops), so an agent can distinguish it from alternatives without opening a schema.

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?

Gives explicit when-to-use guidance: call it after postfjord_upload_media to poll readiness, and use postfjord_preview_post instead when the goal is a channel's own crop. That is clear routing, though there are no explicit when-not conditions (e.g. batch fetching multiple ids) beyond the single pointer to preview_post.

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

All Postfjord 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?