Skip to main content
This page lists every tool available through the TryPost MCP server. Your AI assistant can call any of these tools to manage your TryPost account. To create and publish a post end-to-end:
  1. list-social-accounts-tool — discover connected accounts
  2. list-content-types-tool — discover valid content_type per platform with limits
  3. list-pinterest-boards-tool (if targeting Pinterest) — resolve platforms[].meta.board_id
  4. list-discord-channels-tool (if targeting Discord) — resolve platforms[].meta.channel_id
  5. create-post-tool — create the draft with content + chosen platforms + meta
  6. attach-media-from-url-tool (optional) — attach images or videos from public URLs
  7. request-media-upload-tool + attach-media-from-upload-tool (optional) — upload a local file when no public URL exists
  8. preview-post-tool (optional) — see how each platform will render before publishing
  9. publish-post-tool — publish immediately or schedule for a future time
  10. get-post-metrics-tool (after published) — fetch engagement metrics

Posts

Platforms (read-only)

Signatures

Labels

Social accounts

Workspace

API keys

Per-platform meta (MCP)

platforms[].meta uses the same keys as the REST API. Full tables, limits, and examples: Per-platform meta. Quick checklist for agents:
Enum-like fields are JSON strings. Send "privacy_level": "PUBLIC_TO_EVERYONE", not an integer or a renamed value. Unknown meta keys are dropped.

Notes

  • Workspace scoping — every tool operates on the user’s currently-selected workspace. To act on a different workspace, switch it in the TryPost UI (or, for personal API tokens, create a new key in that workspace).
  • RolesViewers are read-only. They cannot create/update/publish posts, and they also cannot call compose helpers that gate on create-post permission — including list-pinterest-boards-tool and list-discord-channels-tool (error: Not authorized to manage posts.). Owner, Admin, and Member can. See Team.
  • Cross validationcreate-post-tool and update-post-tool reject mismatched combos (e.g. content_type=x_post on a LinkedIn account). Inactive social accounts are also rejected at validation time.
  • Destructive tools — operations that delete data or publish to the world (publish-post-tool, delete-*) are marked IsDestructive, which lets the AI client (ChatGPT, Claude Desktop, etc.) prompt you for confirmation before executing.
  • Local-file uploadsrequest-media-upload-tool returns a single-use signed URL (default TTL 15 minutes). max_bytes is the video ceiling (default 1 GB); per-type caps are in max_bytes_by_type (image / video / document). POST the file as multipart field media, then call attach-media-from-upload-tool with the same upload_token (optional alt for images). See POST /uploads/{token}.
  • Media alt text — image accessibility text lives on media[].meta.alt_text, not on platforms[].meta. Via MCP, set it with attach-media-from-url-tool (urls[].alt) or attach-media-from-upload-tool (alt). The REST create/update endpoints also accept media[].meta.alt_text when hosting from URL.
  • No inline media[] on MCP create/update — unlike REST POST/PUT /posts, the MCP create/update tools do not accept a media array. Always use the attach tools after create.