The Welder MCP server

Identifies the Welder workspace this credential belongs to, so a host that supports several accounts can tell them apart.

No input.

Returns

{ id }

• id is a stable, opaque workspace id resolved only from the validated credential. It never contains an email, the workspace name or a credential.
• Marked as the authenticated profile tool (_meta["openai/profile"]: true). The text content carries the same JSON as the structured result.

get_connected_profile({})

{ "id": "7c1e2a9d-…" }

Start here. The workspace, whether publishing is open right now, this month’s allowance and usage, connected accounts, what each network accepts, and how to hand over files.

No input.

Returns

{ workspace: { id, name, plan_status, limits: { posts, x_credits }, usage: { posts, x_credits }, can_publish }, accounts: Account[], capabilities: { tiktok, instagram, youtube, threads, bluesky, x }, media_hint, links: { app, connect_accounts }, server: { version }, next_step? }

• When can_publish is false, next_step says so: “Publishing is unavailable under this account's current entitlement. Account setup, uploads and validation remain available.” Subscriptions are managed on the Welder website, never through an assistant.
• capabilities is keyed by network, with the same limits as get_capabilities.
• In the simulated review workspace the result also carries review_demo: true and a data_source line, and media_hint explains the sample media. See Review workspace below.

get_context({})

{
  "workspace": {
    "id": "7c1e2a9d-…",
    "name": "Nightshift Studio",
    "plan_status": "active",
    "limits": { "posts": 1500, "x_credits": 100 },
    "usage": { "posts": 3, "x_credits": 8 },
    "can_publish": true
  },
  "accounts": [{ "id": "b2d4…", "provider": "x", "username": "nightshiftHQ", "status": "active", … }],
  "capabilities": { "tiktok": { … }, "instagram": { … }, … },
  "media_hint": "In chat apps without a shell, use create_upload_link and show its URL to the person; then get_upload_link for media ids. With a shell, use create_upload and finalize_upload.",
  "links": {
    "app": "https://weldergtm.com/app",
    "connect_accounts": "https://weldergtm.com/app/accounts"
  },
  "server": { "version": "0.1.0" }
}

Connected accounts with their status and what each can publish. Use the ids as create_post targets.

No input.

Returns

{ accounts: [{ id, provider, username, display_name, avatar_url, profile_url, status: 'active' | 'reauth_required' | 'disconnected', capabilities, connected_at, expires_at, defaults, last_error }] }

• defaults holds provider facts the agent may need, such as the TikTok privacy levels an account offers or the Instagram account type.

A short-lived link (10 minutes) that opens the connect flow for a network in the person’s browser. Show it, then call list_accounts once they finish.

Returns

{ provider, url, expires_in }

• The person signs in on the network’s own screen; the assistant never sees a password. For Bluesky the link opens the app-password form.
• Refused with forbidden in the simulated review workspace, whose sample accounts are provisioned by Welder.

For chat apps without a shell: a link where the person drops their files in the browser. Show it, then call get_upload_link.

Returns

{ upload_link_id, url, expires_in, max_files, kind, next }

• The link works for 2 hours. Its URL is a secret: show it to the person, never log it.

The files the person dropped on an upload link, as media ids for create_post. Wait for them with wait_seconds.

Returns

{ status: 'open' | 'completed' | 'expired', max_files, media: Media[] }

• Only ready media are returned, in upload order.
• Needs the publish scope: a call can mark a link that ran out of time as expired.

Recent uploads, newest first, for requests such as “post my latest upload”. Expired files are left out.

Returns

{ media: [{ id, kind, mime, bytes, width, height, duration_ms, filename, status, error, preview_url: null, expires_at, created_at }] }

For agents with a shell: reserves a media slot and returns a signed upload URL plus the exact curl command to PUT a local file.

Returns

{ media_id, upload: { method: 'PUT', url, headers }, expires_in, curl }

• The upload URL is valid for 2 hours and is a secret. Original media is kept for 7 days; each media post keeps one small image in its history.

curl -sS -X PUT -H "Content-Type: video/mp4" --upload-file "launch.mp4" "<upload url>"

Checks the uploaded object (size, type, and dimensions and duration when possible) and marks it ready. Calling it again on a ready file returns the same media.

Returns

{ media: Media }

• If the file is not there yet the result is media_not_ready, which is safe to retry shortly.

Fetches a public https file into Welder’s storage instead of uploading from disk.

Returns

{ media: Media }

• The simulated review workspace imports only Welder’s public sample files; any file can still be uploaded the normal way.

A dry run of create_post: publishing access and allowance, accounts, media per network, caption lengths, image counts and known limits. Nothing is posted and nothing is used up.

Returns

{ ok, issues, targets: [{ account_id, provider, username, ok, issues, resolved }], cost: { posts, x_credits } }

• Issues with code warning are advice, for example that Instagram shows no caption on Stories. They never block publishing.

Publishes one caption and media set to one or more accounts, now or at schedule_at. Returns at once with the post, or waits up to wait_seconds for the result.

Returns

{ post: { id, status, source, client, caption, title, media, media_count, targets: [{ id, account_id, provider, username, status, attempt, url, platform_post_id, error_code, error_message, ambiguous, published_at, updated_at, kind }], scheduled_at, created_at, updated_at, completed_at } }

• A request that names the exact caption, accounts and time already approves the post; no second confirmation is needed. Ask only about a missing or conflicting detail, such as no caption, an account name that matches two profiles or two different times: a published post can’t always be taken back.
• TikTok privacy and YouTube visibility default to the workspace settings (public unless the person changes them). The AI-generated label is on by default for TikTok and YouTube.
• options.instagram.kind = "story" posts an Instagram Story; a reply option (threads.reply_to_id, x.reply_to_post_id, bluesky.reply_to) answers a comment from list_comments.
• If a target comes back ambiguous, the network may have published it: check the account instead of posting again with a new key.

create_post({
  idempotency_key: "cold-brew-launch",
  caption: "Cold brew season is open. Twelve hours, zero heat.",
  media: ["3ed1…"],
  targets: [{ provider: "tiktok" }, { provider: "youtube" }],
  wait_seconds: 30
})

The current state of a post and each of its targets, with the live link once a network confirms it.

Returns

{ post: Post }

• needs_attention is true while a failed or partly published post has a warning nobody dismissed; attention_dismissed_at says when one was dismissed.
• A TikTok target with url_pending has been posted, but TikTok hasn’t supplied its public link yet (it can still be in moderation). Call again later; a private post may never get a public link, and none is ever made up.
• For a pending TikTok link, get_post may ask TikTok for that post’s status and store the link once it exists. That is the only change it can make: it never publishes, retries or changes usage, so it needs only the read scope. The provider read makes it open-world, and storing the link means it is not read-only. The simulated review workspace never asks TikTok.

Recent and scheduled posts, newest first.

Returns

{ posts: Post[], next_cursor }

Dismisses the warning on a failed or partly published post. The post keeps its results in history and leaves the needs_attention list.

Returns

{ post: Post }

• Does not retry, publish, delete or cancel anything, and contacts no network. The original errors, media and usage stay as they were.
• Safe to call again. A post without an unresolved warning answers conflict. A later explicit retry clears the dismissal, so new failures show up again.

dismiss_post_attention({ post_id: "8c1f…" })

Stops queued and scheduled targets before they go out. Targets already publishing finish.

Returns

{ post: Post }

• Cancelling can’t be undone; schedule the post again to bring it back.

Takes a published post down. Removes it from X and Bluesky; for the other networks the result says to delete it in their app. It can’t be undone: a clear request to delete that post is the go-ahead, and an unclear post or account is worth one question first.

Returns

{ post: Post, results: [{ target_id, account_id, provider, result: 'deleted' | 'already_deleted' | 'unsupported' | 'not_published' | 'failed', message }] }

• A removed copy keeps the status deleted on the post, and its numbers stop updating. Deleting never gives back used posts or X credits.
• Refused with forbidden in the simulated review workspace: its posts never reached a network.

delete_post({ post_id: "8c1f…", account_ids: ["e7a9…"] })

How posts are doing from stored numbers: views, likes, comments, shares and followers per network and account, plus the top posts. A missing number means the network doesn’t share it; the note says why.

Returns

{ period: { since, until }, as_of, posts, measured, totals, interactions, engagement_rate, by_provider: [{ provider, posts, measured, totals, note }], accounts: [{ account_id, provider, username, status, note, metrics, change, captured_at, history }], top_posts: TargetAnalytics[] }

• The period picks posts by publish time; every number is that post’s latest total, not growth inside the period.
• Counters: views, reach, likes, comments, shares, reposts, quotes, saves, link_clicks, profile_visits, follows, engagements, video_views, watch_time_s, avg_watch_time_s. A counter the network does not report is absent, never 0.
• status, per post and account: available, pending, permission_required, unsupported, unavailable or error.

get_analytics({ days: 28, sort: "views", limit: 5 })

One post’s numbers on each network, with the reason when some are missing. refresh asks the networks now; history shows how the numbers grew.

Returns

{ post_id, caption, created_at, targets: [{ target_id, account_id, provider, username, url, status, note, metrics, extra, interactions, engagement_rate, captured_at, next_refresh_at, history? }], totals, as_of }

• Needs the publish scope because refresh: true reads the networks and stores the new numbers; those provider reads make it open-world.
• Numbers are collected about 1 hour, 6 hours, 1 day, 3 days, 7 days, 30 days and 90 days after publishing (Instagram Stories: 1, 6 and 20 hours; X: 1 hour, 1, 7, 29 and 90 days).
• Refreshing too often returns rate_limited with details.retry_after_seconds. In the simulated review workspace refresh is ignored and the fixed sample numbers are returned.

get_post_analytics({ post_id: "8c1f…", refresh: true, history: true })

Replies under a published post, network by network. To answer one, call create_post with that account as the target and the comment id in the option named by reply_option.

Returns

{ post_id, targets: [{ target_id, account_id, provider, username, status, note, reply_option, comments: [{ id, author: { username, display_name, avatar_url }, text, created_at, likes, replies, url, parent_id, is_own, hidden }] }] }

• Needs the publish scope: each read of X replies uses 1 X credit, and a network read can refresh the account’s sign-in. Reading comments from the networks makes it open-world.
• Readable today: Bluesky, YouTube (read only), X with the account’s X entitlement (the last 7 days), and Threads where the connection holds the replies permission. Instagram answers permission_required and TikTok unsupported.
• reply_option is threads.reply_to_id, x.reply_to_post_id or bluesky.reply_to; null where Welder cannot reply (YouTube). Send an answer when the person asks for it with its words; when they ask for a draft, write it in the chat and send nothing.

list_comments({ post_id: "8c1f…", account_id: "b2d4…" })
create_post({
  caption: "Not yet, but it’s on the list!",
  targets: [{ account_id: "b2d4…" }],
  options: { threads: { reply_to_id: "17890…" } }
})

What every network accepts: media types, sizes, durations, image counts and caption limits. Static, the same for every workspace.

No input.

Returns

{ providers: { tiktok: { text_only, video: { max_bytes, min_duration_s, max_duration_s, mimes }, images: { max_bytes, min_count, max_count, mimes }, mixed_carousel, caption_max, title_max, story?, notes }, … } }