Skip to main content

Overview

Once connected, your assistant has access to the tools below. You don’t need to call them by hand — just ask in plain language (“draft a LinkedIn post for Friday,” “show me last month’s engagement”) and the assistant picks the right tool.
Always start with workspaces. If this is a new session, ask the assistant to “list my Ordinal workspaces” first. It needs to know which workspace you want before it can do anything else.

Discovery

Posts and ideas

Post statuses

ordinal_create_post and ordinal_manage_post accept a status of Tentative, ToDo, InProgress, ForReview, or Scheduled, so the assistant can move posts through the same workflow statuses you use in the app. New posts default to ToDo. Posted can’t be set through MCP because Ordinal applies it only after a post publishes. For example, ask “move my draft about the pricing launch to For Review” and the assistant calls ordinal_manage_post with status: "ForReview".

Media

For a local file, the assistant calls ordinal_create_upload with filename, mimetype, and size, POSTs the file to the returned uploadUrl with params and signature, then polls ordinal_get_upload until status is ready.

Analytics

Collaboration

Team engagements

Slack boosts

Amplify

Both tools are read-only and require Amplify to be enabled on your workspace. Like permalinks point at the campaign’s target post; comment, repost, and post permalinks point at the engager’s own content. ordinal_list_amplify_engagers is paginated (default 50 per page, max 100) and accepts an optional action filter. The filter only narrows which people are returned — each person’s list of actions still includes everything they completed on the link. For example, ask “who engaged with our launch Amplify link?” and the assistant calls ordinal_list_amplify_links to find the link, then ordinal_list_amplify_engagers to return names and permalinks your team can follow up on.

LinkedIn Monitoring

These tools appear only for workspaces where LinkedIn Monitoring is enabled, and they act on the same inbox you see in the app. Comments are paginated 10 roots per page by default (max 50); posts and mentions are 20 per page (max 50). Replies and reactions are posted from a scheduling profile — get the profileId from ordinal_get_workspace_context. Replying to a comment automatically resolves that comment. Replying to a reply still posts on the thread root. Commenting on a mention does not auto-resolve it — resolve separately when you’re done. LinkedIn reactions accept Like, Celebrate, Love, Insightful, Support, or Funny; sending the same reaction again removes it. For example, ask “triage today’s LinkedIn comments — reply to anything from a customer and resolve the rest” and the assistant lists unresolved posts, pages through comments, replies where needed, and marks the others resolved. ordinal_get_linkedin_mention under Platform utilities is different: it looks up a LinkedIn user or company URN to mention in post copy, not an inbox notification.

Labels

Platform utilities

Asking the assistant things

You don’t call these tools by name — you describe what you want. Examples:
  • “Create a LinkedIn post for next Tuesday about our new pricing, in the Launch campaign.”
  • “Archive the drafts I wrote last month that don’t have a label.”
  • “Show me which posts are waiting on approval from Sarah.”
  • “Give me the last 30 days of follower growth on LinkedIn.”
  • “Show me how the LinkedIn copy on this post changed between the last two saves.”
  • “List everyone who commented through our launch Amplify link, with links to their comments.”
  • “Reply to any unresolved LinkedIn comments on our launch post, then resolve the rest.”
The assistant picks the tools, fills in the arguments, and shows you the result.