Tools
Tools available through the dopost MCP server.
Tools available through the dopost MCP server.
The dopost MCP server exposes focused tools for publishing, scheduling, analytics, accounts, media, and public downloads.
| Tool | What it does |
|---|---|
publish_post | Save drafts, publish or schedule groups, reply, or create a thread. |
list_posts | List posts with status and pagination filters. |
get_post | Get complete details for one post. |
reschedule_post | Change the date of a scheduled post. |
delete_post | Delete a post or cancel its schedule. |
Before publishing or scheduling with publish_post, call get_platform_limits for each distinct destination platform. Check the text and the selected post type's requirements, including thread entries and per-account overrides in groups. If a known limit is exceeded, explain the affected field, actual value and allowed limit before attempting to publish.
Only compare file properties when verified metadata is available; do not infer dimensions, duration or codecs from filenames or URLs. A successful upload_media call confirms file receipt and upload checks, but does not confirm compatibility with a destination. The server inspects received files and applies the web composer's validation before creating posts, returning detailed errors when checks fail. Drafts may contain incomplete platform content.
These instructions guide the MCP agent; the server does not automatically call get_platform_limits on its behalf. After deployment, refresh the client's cached tools to load the updated instructions.
Call publish_post once with posts: [{ accountId, ... }, ...] instead of accountId to create one group for up to 20 accounts in the same workspace. Top-level content is shared by default; each item can replace text, media, platformOptions, replyTo or thread. Put draft, publishAt and timezone at the top level. Shared media URLs are imported once. Inspect each returned postId for publishing outcomes; groupId identifies the dashboard group. A validation failure creates no posts and identifies the failing account and field. See Post groups. delete_post on a member deletes the entire group; rescheduling changes only the requested member.
Call publish_post with draft: true, an accountId, and optional text, media, thread and platformOptions. Omit publishAt. The tool returns status: "draft" and a postId without publishing or scheduling anything. Use get_post or list_posts with status: "DRAFT" to retrieve it, and open it in the dopost dashboard to continue editing or publish it. Incomplete platform content can be saved; attachments still undergo size, format and integrity checks. See Save a draft.
| Tool | What it does |
|---|---|
create_recurring_post | Create a daily, weekly, or monthly recurring post series. |
list_recurring_posts | List recurring series, their next run, accounts, and latest result. |
update_recurring_post | Update future content, media, cadence, or the next occurrence. |
| Tool | What it does |
|---|---|
list_workspaces | List the workspaces available to the current MCP connection. |
list_accounts | List social accounts across accessible workspaces. |
list_x_communities | List Communities saved for a connected X account. |
add_x_community | Validate and save a Community for an X account. |
remove_x_community | Remove a Community from an X account's saved catalog. |
get_platform_limits | Return content and media limits for a platform. |
Hosted OAuth connections can access only authorized workspaces where the user still has access. Newly joined workspaces remain disabled until enabled in Settings → MCP connections. List tools return workspace metadata and accept workspaceId when a request must be narrowed. Resource-based actions such as publishing infer the workspace from the selected account or resource. Local API keys remain restricted to the workspace that issued them.
Call list_x_communities with an X accountId, present the returned Community names to the user, and pass the selected name to publish_post. The MCP server resolves the ID internally:
{
"accountId": "<xAccountId>",
"text": "Community update",
"platformOptions": {
"communityName": "Builders Community",
"shareWithFollowers": false
}
}{
"accountId": "<xAccountId>",
"text": "Community update",
"platformOptions": {
"communityName": "Builders Community",
"shareWithFollowers": false
}
}shareWithFollowers defaults to true. Use communityId only as a technical fallback when multiple saved Communities have the same name. The selected X account must be a member of the Community and have permission to post there.
If list_x_communities returns no entries, ask the user for a Community URL and call add_x_community. After it returns the validated display name, use that name as publish_post.platformOptions.communityName.
Before calling remove_x_community, confirm the removal with the user. Prefer communityName; the technical communityId is needed only when duplicate names make the selection ambiguous.
| Tool | What it does |
|---|---|
get_analytics_overview | Read account KPIs, rankings, comparisons, and data availability. |
list_post_performance | List dopost-published posts sorted by performance. |
get_post_performance | Read performance history and collection progress for one post. |
get_content_insights | Read Best Time, Best Day, Format Opportunity, and Platform Pulse. |
get_audience_analytics | Read the available audience breakdowns for one account. |
Analytics tools require analytics:read and an active paid plan. Daily series are omitted by default; set includeSeries: true for ranges up to 90 days. Post lists return at most 20 items per call.
Audience analytics currently support Facebook and Instagram accounts. TikTok Analytics remains unavailable until the integration is enabled and the account has been authorized for the required Analytics permissions.
Analytics tools missing
Existing API keys and OAuth authorizations do not include the new analytics:read permission automatically. Create a key with this permission or reconnect the MCP client and approve it. If the permission is already present, reconnect the client to reload the available tools.
| Tool | What it does |
|---|---|
list_media | List files in the dopost Media library. |
delete_media | Delete a file from the Media library. |
upload_media | Upload a local file. Available only on the local stdio server. |
| Tool | What it does |
|---|---|
get_social_media_download_options | Inspect available MP4 and MP3 formats for a public URL. |
prepare_social_media_download | Return a temporary URL for the selected format. |
The hosted server does not expose upload_media because a remote process cannot read a path on your computer. Pass a public HTTPS URL to publish_post or use the REST presigned-upload flow with purpose: "post". External post attachments are imported into dopost storage before accepting the post for publishing or scheduling. Local upload_media defaults to purpose: "library"; use purpose: "post" for a post attachment. Upload errors are returned to the agent and must be resolved before publishing.
publish_post accepts two optional fields:
thread: ordered follow-up posts for X, Threads, and Mastodon. dopost publishes them as a reply chain in a single publishing request.replyTo: the external platform post ID to reply to on X or Threads. This is not a dopost post ID.For a new thread, prefer one publish_post call with text for the first post and thread for the remaining posts. This avoids waiting for the first platform post ID before continuing the chain.
{
"accountId": "<xAccountId>",
"text": "First post",
"thread": [
{ "text": "Second post" },
{ "text": "Third post", "media": ["<publicMediaUrl>"] }
]
}{
"accountId": "<xAccountId>",
"text": "First post",
"thread": [
{ "text": "Second post" },
{ "text": "Third post", "media": ["<publicMediaUrl>"] }
]
}thread accepts 1–20 follow-up posts and up to four public media URLs per item. On X and Threads, include replyTo alongside thread to start the chain as a reply to an existing platform post.
Missing fields in your AI client
The current MCP server includes list_x_communities, and the publish_post schema includes replyTo, thread, and platformOptions.communityName. If these are missing, refresh the MCP tools or reconnect dopost to clear the cached schema.
An immediate publish request returns processing when dopost accepts the post for publishing. Scheduled posts return scheduled. Publication is confirmed when get_post reports PUBLISHED. Use get_post with the returned postId to check the final result.
If a call returns no tool result and the entire dopost tool namespace temporarily disappears, the client is likely refreshing its MCP connection or OAuth session. That alone is not evidence that dopost rejected the post. When the tools return, check recent posts with list_posts before retrying: the original publish request may have been accepted even though its response was lost, and retrying it blindly can create a duplicate. API or MCP rejections include an explicit error response; keep that message and the request ID when contacting support.
publish_post accepts all four types and their options. get_analytics_overview supports GOOGLE_BUSINESS, Search/Maps and action metrics; get_google_business_search_terms returns paginated monthly keywords and privacy thresholds. Unzoned dates use the workspace timezone; publish/reschedule accept an optional timezone override. Refresh cached tools after this version is deployed.
Publishing uses the same validation rules as the web composer after inspecting actual file bytes. Blocking failures return isError: true, a readable explanation in content, and the API error in structuredContent, including httpStatus, errorCode, stage, issues, and retryable. Inspect each issue's file name, actual value and expected limit; correct the attachment before retrying a non-retryable validation failure. Recommendations remain non-blocking and appear in warnings on accepted posts. Query get_post for the recorded error if an accepted post fails later.
Attachment import errors also preserve fileName, field, threadIndex, mediaIndex, stage and retryable. See File integrity and import failures for source, storage and video integrity error codes.