Skip to main content
Glama
Sign In
Postoria MCP Server

Postoria MCP Server

Official
by postoria-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

complete_media_upload

Complete a media upload after sending the file bytes to the signed URL. Finalize the process to make the media available in Postoria.

Instructions

Complete a media upload after the raw file bytes have been uploaded to the signed upload URL.

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": {
      "workspace_id": "<workspace_id>",
      "media_id": "<media_id>"
    },
    "name": "complete_media_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_idYesPostoria media ID.
workspace_idYesPostoria workspace ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose what happens if called out of order, error states, or any side effects. It only states the action without behavioral context.

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 description is a single, well-structured sentence with no redundant information. It conveys the essence efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description lacks details on the result, error conditions, or workflow context. It is insufficient for a tool that is part of a multi-step process.

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 description adds no extra meaning to the parameters beyond what is in the schema. Baseline score of 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?

The description states a specific verb and resource ('Complete a media upload') and includes the prerequisite ('after the raw file bytes have been uploaded to the signed upload URL'), distinguishing it clearly from related tools.

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 description implies when to use (after uploading bytes) but does not explicitly mention when not to use or provide alternatives among sibling tools like create_media_upload or upload_media_from_file.

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

Deploy Server

Other Tools