PostRite

List media files

list_media

Read-only

List the organization's media library, newest first. It holds images and videos, which posts publish, and audio files and PDF documents, which are there for chat (inbox replies and flow steps) and which a post refuses. Check each file's mimetype, and use the id of an image or a video as a mediaId when creating or updating a post.

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

Name	Required	Description
`page`	No	Page number, 1-based (default 1)
`limit`	No	Page size (max 100, default 50)
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.

Output Schema

Name	Required	Description
`page`	No
`files`	No
`limit`	No
`total`	No
`totalPages`	No
`storageUsed`	No	Bytes
`storageQuota`	No	Bytes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: default newest-first ordering and the behavioral distinction that audio and PDF files are rejected by a post while used in chat. It omits pagination behavior, a minor gap given the schema carries page/limit.

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

Conciseness4/5

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

Purpose and ordering are front-loaded, and every sentence carries information about content types or downstream id usage. The middle sentence is somewhat tangled with stacked relative clauses ('which are there for chat ... and which a post refuses'), costing a point on clarity.

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 simple read-only list with full schema coverage and an output schema, the description covers what the library contains, how it is ordered, and how ids are reused. Pagination is left to the schema, so the definition is functionally complete.

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 page, limit, and organizationId are already documented in the schema, and the description adds no parameter-level detail. Baseline 3 applies when the schema does the heavy lifting.

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 (list) and resource (organization's media library) plus scope details: newest-first ordering and the exact file types held (images, videos, audio, PDFs). An agent can immediately distinguish this read operation from siblings such as delete_media, update_media, import_media_from_url, or get_media_usage.

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 clear usage context: check each file's mimetype, and use the id of an image or video as a mediaId when creating or updating a post. It also implies which asset types are usable in posts versus chat. It does not explicitly name alternative tools or when not to call this one, which keeps it short of a 5.

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

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