Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get recent media from connected accounts

get_media
Read-only

Retrieve recent media (videos, photos, text) from a profile's connected social accounts to review existing content before posting. Supports paginated browsing across platforms.

Instructions

Retrieve recent media (videos, photos, text posts) pulled directly from a profile's connected social accounts. Supports instagram, tiktok, youtube, linkedin, facebook, x, threads, pinterest, bluesky, reddit. Useful for browsing what already exists on a platform before posting more. Paginated: the response carries pagination = { limit, next_cursor, has_more }; pass next_cursor back as cursor for the next page (the last page returns next_cursor null and has_more false).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoProfile username to scope the query to.
limitNoItems per page. Defaults to 25 and is clamped to 1-100. Per-platform caps: TikTok 20, YouTube 50, everything else 100.
cursorNoOpaque cursor from a previous response's `pagination.next_cursor`. LinkedIn, Discord and Telegram do not support cursors — passing one there fails with HTTP 400; use `limit` alone on those platforms.
page_urnNoLinkedIn only. Numeric organization ID (e.g. '12345'), full URN ('urn:li:organization:12345'), or 'me' to force the personal profile. When omitted, accounts linked as an organization admin auto-resolve to the first administered organization; otherwise the personal profile is used.
platformNoRestrict to a single platform key.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Adds significant context beyond annotations: explains data source (connected accounts), pagination mechanics, platform-specific cursor support, and per-platform caps. Annotations are readOnlyHint=true and destructiveHint=false, which the description respects.

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?

Single paragraph packed with essential information, no filler. Every sentence provides value.

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?

Given the complexity (5 params, many platforms, pagination), the description covers all key aspects: purpose, supported platforms, pagination, platform-specific constraints, and parameter semantics. Output schema exists separately.

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

Parameters5/5

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

Schema coverage is 100%, but description enriches with platform-specific details: per-platform limits for limit, cursor failure info for certain platforms, and LinkedIn-specific behavior for page_urn.

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 clearly states the tool retrieves recent media from connected social accounts, lists supported platforms, and distinguishes it from sibling upload tools.

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?

Provides a clear use case ('browsing what already exists on a platform before posting more') and explains pagination. Could explicitly mention when not to use (e.g., for analytics), but overall helpful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Upload-Post/upload-post-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server