Inexra

Snapshot the active workspace's deal pipeline: overdue deliverables (deadline passed, not yet posted/approved) and unpaid deals (paymentStatus UNPAID, not archived). Use when the user asks about priorities, follow-ups, brand work, or money outstanding.

get_pipeline_status

Per-post content performance for this workspace. Use for any question about individual posts: "which post did the best?", "what were my top posts last month?", "how did my reels do?", "what should I post more of?", "show me my worst performers". Returns one row per post with reach, views, likes, comments, saves, shares, and engagement rate, plus replies, exits and exit rate for stories and follows/profile visits where reported, plus an optional per-format comparison. For stories, pass format "STORY": replies and exit rate describe a story far better than likes or saves. This is the per-post companion to query_metrics, which returns workspace totals, use query_metrics for "how much reach did we get", and this for "which post got it". Some posts may be missing individual metrics depending on what the connected account exposes; the result says so explicitly. Never present a missing metric as zero.

get_post_performance

Read what is inside one report: its written sections, each metric block's figures, the posts it features, and a plain-language summary of the headline numbers. Published reports return the frozen figures the client saw; drafts return live figures. Use for 'what did the September report say', 'summarise the report for the client', or before drafting a note to send with a report. Takes a reportId from get_report_status.

get_report_contents

Report documents in the active workspace: which are still drafts, which are published, whether the client has opened the share link, and when each was last published. Use when the user asks about reports, what is owed to a client, what is unfinished, or whether a client has seen anything.

get_report_status

Look up posts in this workspace. Use window='recently_created' (default) for 'the posts I just scheduled' or 'what did we schedule?'. Use window='upcoming' for anything about the calendar ahead: 'what's going out next week', 'what is scheduled for Friday', or to find a post the user wants to change. Read-only. Changing or cancelling a scheduled post is done in Inexra.

get_recent_scheduled_posts

List the client workspaces this Inexra user can open, with ids and names, which one they last had open, and whether it can be used from here (it needs AI access on and a paid plan). Call this first when the user names a client, then pass its id as `workspace` to the other tools.

list_workspaces

Stage a DM reply for the user to send. Use when the user asks you to reply, answer or respond to someone (not merely to draft). Read the thread with get_conversation first and reply to its latestInboundMessageId. For 'draft a reply' with no intent to send, return a draft instead. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_dm_reply

Stage a PUBLIC reply to a comment on a post, for the user to post. Get the commentId from get_comments. A public reply is visible to everyone, so keep it short and never include anything private (prices agreed in DMs, contact details). Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_comment_reply

Stage moving a pipeline deal to another stage ("mark the Oat & Co deal as won", "move it to Negotiating"). Get the dealId from find_contacts. Pass the target stage by name; it must be a stage of the deal's own pipeline. Applied when the user confirms, and can be undone. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_deal_move

Stage changing an existing deal ("they agreed 2,400", "mark the Oat & Co deal invoiced", "contract is signed", "it closes on the 30th", "add a note that they want usage rights"). Get the dealId from find_contacts. Pass only the fields that change. To move a deal between stages use stage_deal_move instead. Applied when the user confirms, and can be undone. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_deal_update

Stage adding a NEW deal to the pipeline ("add Oat & Co to the pipeline", "start a deal for this DM", "log that collab"). Call find_contacts first: if a deal with them already exists, change it with stage_deal_update instead. When the deal comes out of a DM, read the thread with get_conversation and pass its latestInboundMessageId as messageId so the deal links to the conversation. Only include a value, type, date or deliverable that was actually stated: never estimate a number. Created when the user confirms, and can be undone. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_deal_create

Stage creating a client report as a DRAFT for a period ("draft the September report", "start this month's report"). The draft is built from a report template and opens with a summary paragraph the server writes from the real figures. It is never published or sent by you: that stays the user's decision in the report editor. Created when the user confirms, and can be undone. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_report_draft

Stage a to-do for someone on the team, or for the user ("remind me to send Acme the deck Friday", "have Sam get the photos from the client by Tuesday", "every month remind Dana the report is due on the 1st"). It lands on that person's My work with the date. Use repeat for a to-do someone must do on a schedule. Attach it to what it is about when there is one: a dealId or a person's contactId from find_contacts ("remind me to call Ally back Friday" goes on Ally's contact), a postId from get_content_plan or get_recent_scheduled_posts, or a messageId from get_conversation. Added only when the user confirms. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_task_create

Stage asking a teammate to review a post before it goes out ("ask Dana to look at Friday's post"). Get the postId from get_recent_scheduled_posts or get_content_plan, and name the reviewer as the user did. Sent when the user confirms, and can be withdrawn. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_review_request

Stage adding content ideas to the Plan board (up to 12). Use when the user wants ideas saved or added to the plan, not merely listed. Call get_content_plan first and assign each idea to the pillar it serves, by name. Ideas are notes on the board: nothing is scheduled and nothing can publish. Added when the user confirms, and can be undone. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_plan_ideas

Stage linking a DM conversation to the post it came from, so it counts toward that post in Analytics and client reports as confirmed by the team. Use when the user says which post someone came from ("she found us from the SPF reel", "link this to Tuesday's carousel"), or asks you to work it out. Read the thread with get_conversation first: its sourcePost shows any existing link and suggested posts, with the caption words each one shares with what the person wrote. Pass postId: null to remove the team's link. A conversation linked automatically (a story reply, a share, or a reply to a comment) cannot be changed. Only stage when the user asked for the link, or confirmed your guess; never on a hunch alone. Over this connection the action is staged, not done: it waits in the Inexra AI queue in Inexra (Waiting for your OK) for 24 hours and happens only when someone confirms it there. Tell the user that, and never say it was sent, posted, moved or created.

stage_conversation_post_link

Search the active workspace's inbox. Filter by free-text content, platform, sentiment, tag, sender, reply/read state, priority, or recency. Returns up to 50 messages with key fields. Use this when the user asks about specific messages or wants to find content matching criteria.

search_messages