Every tool

127 tools, grouped by the permission that reaches them, which is the same grouping the endpoint reference and the API key picker use. https://mcp.reelwire.io/mcp/all lists all of them that your key may use; https://mcp.reelwire.io/mcp lists the 61 marked Yes under At /mcp, the everyday ones, and reaches the rest through reelwire_find_tools and reelwire_use_tool (see Which tools it lists). The last column is the route each tool calls, so a workspace already driving Reelwire over HTTP can find the tool for something it does today.

Every tool carries the MCP annotations for what it does to the world (only reads, changes or removes something, reaches outside the workspace), which is how your app decides when to ask you first. Tools merged into another, and the retired ones, still answer by name and are listed nowhere.

Every tool is the API and nothing more. The server holds no key of its own: every request acts as the caller's own Reelwire API key, sent with it or minted for them by an OAuth connection (on their own machine, the key the server was started with), and passes the call through. Whatever that key may do, the assistant may do; whatever it may not, the assistant is refused with the name of the permission that is missing. See Permissions.

note

Generated from a running server, so this is what it actually serves. 127 tools cover every route a workspace key may call. Rotating the webhook signing secret is not a key's to call at all.

Overview

Posts

Needs Posts.

Tool	What it does	At /mcp	API equivalent
reelwire_archive_post	Files a channel's post away: it leaves reelwire_list_posts, which lists the active ones unless asked for archive archived.		/v1/jobs/{id}/unarchive /v1/jobs/{id}/archive
reelwire_cancel_post	Stops one channel of a post that has not been handed over yet: its render, its approval request, and its hand-over if that is still waiting to go.	Yes	/v1/jobs/{id}/cancel /v1/whoami
reelwire_delete_post	HANDS A REQUEST TO THE OUTSIDE WORLD: it asks for this channel's post to be taken down, the ways the channel has switched on (never one that is off): its email goes as "Please take this post down", the webhook receives a post.delete, and the platform connector deletes a post it made itself, where the platform lets an app do that.	Yes	/v1/jobs/{id}/delete
reelwire_download_post_clip	A post's video for the person to have.		/v1/pipeline/{id} /v1/jobs/{id}/download
reelwire_download_post_package	One post's package: its description, hashtags, brand text, channel and times, which is what somebody takes away to post by hand somewhere Reelwire does not reach.		/v1/posts/{id}/package
reelwire_list_channel_posts	One row per channel post: one piece of content for one channel in one language and shape, with its caption, hashtags, state, when it is scheduled, when it was handed over and the link somebody reported for it.		/v1/posts
reelwire_list_posts	Every post from arrival to published, newest first, ONE ROW PER POST: one piece of content, with its channels inside it in channels.	Yes	/v1/jobs
reelwire_overview	The counts across the pipeline: waiting, rendering, awaiting approval, scheduled, published, failed.	Yes	/v1/overview
reelwire_pipeline	A live look at the two lanes: clips being rendered and posts being published, with counts by state, what is in flight, what finished recently and how long each has been at its stage.		/v1/pipeline
reelwire_post_trace	Everything about one channel of a post in one answer: what arrived and when, the brand and channel, the template, variant and version, the render with each output and its errors, the approval and who decided it, what people said about it (comments, oldest first), and the post with its captions, link and every hand-over it was part of (email, webhook and platform connector, each with its attempts).	Yes	/v1/pipeline/{id}
reelwire_report_post	What a webhook receiver calls once it has acted on a hand-over, and what an assistant calls after posting one itself: for one channel's post, published (with its url and the platform's own id where known), skipped (deliberately not posted), failed (with the reason, which the Posts screen shows) or deleted (taken down after a delete was handed over).	Yes	/v1/posts/{id}/report
reelwire_repost	HANDS OVER AGAIN: the same clip and text, for the same channel, as a new post of its own, handed over now the ways the channel has switched on (a platform connector that is on posts it on the platform again).		/v1/jobs/{id}/repost
reelwire_retry_post	HANDS OVER AGAIN, AND MAY POST PUBLICLY: a channel's post that FAILED (its email, webhook call or platform connector never got through, or its receiver reported it failed) is handed over anew, as it reads now, the ways the channel has switched on or the ones named of them.	Yes	/v1/jobs/{id}/retry-render /v1/jobs/{id}/retry
reelwire_reuse	Reads what a post, a rendered clip or an export was made from, to make it again with a change: its template, VARIANT and build, brand, shape, language, and its content in the template's own shape with locales for every further language.	Yes	/v1/jobs/{id}/reuse /v1/media/renders/{id}/reuse /v1/direct-export/video/{jobId}/reuse
reelwire_update_post	HANDS A CHANGE OVER: the new text, and a new video where given, go the ways the channel has switched on (never one that is off): its email goes as "This post changed", the webhook receives a post.update, and the platform connector changes the text of a post it made itself, where the platform lets an app do that (never its video).	Yes	/v1/jobs/{id}/kit-link /v1/jobs/{id}/comments/{commentId}/delete /v1/jobs/{id}/comments/{commentId} /v1/jobs/{id}/comments /v1/jobs/{id}/update

Posts - Approvals

Needs Posts - Approvals.

Tool	What it does	At /mcp	API equivalent
reelwire_decide_approval	Decides one approval.	Yes	/v1/approvals/{id}
reelwire_list_approvals	Everything waiting for somebody to clear it before it can go out, oldest first, because a queue is worked from the front.	Yes	/v1/approvals

Schedule

Needs Schedule, which is read only.

Tool	What it does	At /mcp	API equivalent
reelwire_calendar	The posting calendar for a window: which channel publishes what and at what time, worked out from every subscription's schedule, as the dashboard's Schedule shows it.	Yes	/v1/calendar/still /v1/calendar/export/jobs /v1/calendar/export/jobs/{jobId}/cancel /v1/calendar/export/jobs/{jobId} /v1/calendar/export/jobs/{jobId}/file /v1/calendar/export/link /v1/calendar/export /v1/calendar

Compliance

Needs Compliance, which is read only.

Tool	What it does	At /mcp	API equivalent
reelwire_compliance	Reads the compliance record (Enterprise): an entry for every clip Reelwire makes, a post's clip as it is rendered and every video exported (Create clip, an AI assistant, the API), every post handed over, every update, delete and resend, every approval decision, every delivery's outcome, every report of where a post stands and every change to a channel's approval, each sealed into the workspace's signed chain, time-stamped by an outside authority once a day and kept ten years, a video's with three frames of it.		/v1/compliance /v1/compliance/export /v1/compliance/export/link /v1/compliance/audit /v1/compliance/records/{id} /v1/compliance/records

Library

Clip studio

Needs Clip studio.

Tool	What it does	At /mcp	API equivalent
reelwire_catalogue	Every ready-made feed Reelwire ships, by data source: each source's markets and each feed's id, slug, title, description and the templates that draw it.		/v1/catalogue
reelwire_list_templates	The templates offered to this workspace, one short entry each: what it draws, its variants (styles of one content for a collection, different posts for a vertical such as Finance), the shapes it draws, how long its clips run, its newest version and its kind: style-and-format (one format of content, a chart, a list, a countdown, in the styles that suit it), looks (the brand's own parts in many styles: Stinger, Intro, Outro, Background, and Overlay for a video of theirs) or package (different posts in one style, made for this workspace where individual says so).	Yes	/v1/templates
reelwire_plan_export	CALL THIS BEFORE reelwire_export_video, every time, for the variant you will render: a template's variants can take entirely different fields (each of Finance's ten is a different post).	Yes	/v1/templates /v1/media /v1/brands/{id} /v1/quick-start/profile
reelwire_request_custom_design	SENDS AN EMAIL TO REELWIRE, ONLY ON THE PERSON'S YES: when they like none of the styles you showed them in their own brand, ask whether they would like a design made especially for them, and if they say yes, send this.	Yes	/v1/templates/custom-design
reelwire_template_format	The JSON schema of one template's inputs, for one variant, with an example that passes the template's own check, so it is a safe start to change from.	Yes	/v1/formats/feed/{feedId} /v1/formats/feed/{source}/{format} /v1/formats/template/{templateId}
reelwire_template_reference	Every variant of one template and every version of each, newest first, with the shapes each draws.	Yes	/v1/templates/{templateId}/reference/{ratio}/still /v1/templates/{templateId}/still/{ratio} /v1/templates/{templateId}/reference /v1/templates/{templateId}/reference-sheet /v1/templates/{templateId}/reference/{ratio}
reelwire_validate_content	Checks content against the template build it would draw, exactly as rendering a clip or saving a post checks it, and stores nothing: every field's shape and length, and every picture it names (media://...), which must be in the media library.	Yes	/v1/templates/{templateId}/validate

Clip studio - Create clip

Needs Clip studio - Create clip.

Tool	What it does	At /mcp	API equivalent
reelwire_discard_export	DELETES AN EXPORT FOR GOOD: stops it if it is still rendering and removes the kept copy, whatever state it is in.		/v1/direct-export/video/{jobId}/discard
reelwire_download_export	The finished export as an .mp4, the video file itself: no zip, nothing to unpack.	Yes	/v1/direct-export/zip /v1/direct-export/zip/link /v1/direct-export/video/{jobId}/link /v1/direct-export/video/{jobId}/download
reelwire_export_keyframes	Draws the frames you name as stills and ANSWERS WITH THE PICTURES, up to six, which you can look at: the cheap way to see what a template does with some content in a brand before spending a render, since stills are not counted against the allowance.	Yes	/v1/direct-export/keyframes
reelwire_export_queue	The workspace's exported videos, what Clip studio's Exported videos card lists, newest first: every export still waiting or rendering (with progress, and how many clips are in front of it), each that failed in the last two hours (with the reason), and the kept ones.	Yes	/v1/direct-export/queue
reelwire_export_status	The state of one export: queued, rendering, succeeded, partial, failed, timed_out or cancelled, with progress from 0 to 1 and, while it waits, how many clips are in front of it on that machine.	Yes	/v1/direct-export/video/{jobId}
reelwire_export_timing	Works out how many frames this template will draw for this content, and how long that is in milliseconds, without rendering anything and without spending a render.		/v1/direct-export/timing
reelwire_export_video	BEFORE CALLING THIS, PLAN IT WITH THE PERSON: call reelwire_plan_export, ask for the content it lists (including the optional figures, points, pictures and source, not only a headline), get their pictures into the media library, check the content with reelwire_validate_content for the same template and variant (fix what it names; it costs nothing), and confirm a summary.	Yes	/v1/direct-export/video
reelwire_export_videos	Draws the one content in EVERY shape of ratios and EVERY language of locales, one video each (at most 24).	Yes	/v1/direct-export/batch
reelwire_list_exports	Every kept export of this workspace, newest first: template, variant, shape, language, length, and when it was made, with a link to play and download it that lasts as long as the export is kept.	Yes	/v1/direct-export/videos
reelwire_list_renders	Every clip this workspace has had drawn, newest first: what drew it, which template and version, how far it got, how long it took and whether its video is still stored.		/v1/render-jobs/{id}/package /v1/render-jobs

Media

Needs Media.

Tool	What it does	At /mcp	API equivalent
reelwire_asset	What a rendered clip is: its shape, language, size, duration, type and checksum, with a signed URL anybody can fetch or open.		/v1/assets/{id}
reelwire_copy_clip_to_library	Puts a copy of one rendered clip (a post's clip or a kept export) into the media library as a file of its own, by the library's own rules: the storage allowance and the size of one file.	Yes	/v1/media/renders/{id}/copy /v1/direct-export/video/{jobId}
reelwire_delete_media	Deletes the file itself.		/v1/media/{id}/delete
reelwire_delete_rendered_clip	Deletes a clip Reelwire drew, or a kept export, freeing the storage it held.		/v1/media/renders/{id}/delete
reelwire_download_asset	One file, a media library file or a rendered clip, for the person to have: over a hosted connection a signed link to give them, on their own machine (stdio) the file itself, written beside them.		/v1/assets/{id} /v1/media /v1/media/renders /v1/assets/{id}/download
reelwire_import_media	Fetches one file from a public https address (a picture on the person's website, a logo they linked, an image they host) and adds it to the workspace's media library, answering with the file and its ref (media://...), which is what a template's picture field and a brand slot take.	Yes	/v1/media /v1/media/import
reelwire_list_media	The images, video, sound and fonts in the library, which a template's content can point at, and how much of the workspace's storage they use.	Yes	/v1/media/renders /v1/media/feed-pictures /v1/sound-library /v1/media
reelwire_media_upload_link	FOR FILES THE PERSON HAS: on their computer, attached in this chat, or on the machine you are running on.	Yes	/v1/media/upload-link
reelwire_media_uses	Every brand and post that points at one file in the media library.		/v1/media/{id}/uses
reelwire_rename_media	Changes what a file is called.		/v1/media/{id}/rename

Publication

Brands

Needs Brands.

Tool	What it does	At /mcp	API equivalent
reelwire_brand	Everything one brand holds: its name, whether it is in use, and the whole STYLE object, which is what a clip actually wears: identity (the lines it draws), palette (the colours it was given) and the colours worked out from them, text (faces and sizes), its logo, badge, background, stinger, intro and outro, sound, the transition between them, and the post text that goes out with every post.	Yes	/v1/brands/kits /v1/brands/{id}/kit/jobs /v1/brands/{id}/kit/jobs/{jobId}/cancel /v1/brands/{id}/kit/jobs/{jobId} /v1/brands/{id}/kit/jobs/{jobId}/pictures/{index} /v1/brands/{id}/kit /v1/brands/{id}/kit/jobs/{jobId}/file /v1/brands/{id}/kit/link /v1/brands/{id}
reelwire_brand_palette	Give it a brand colour or two and it answers with the complete set a template needs: the surfaces, the ink that stays readable on each of them, and the accents, and says where a colour given was adjusted to stay readable.	Yes	/v1/brands/palette
reelwire_create_brand	A brand is what a clip wears: names, colours, type, logo, the legal line and its films.	Yes	/v1/brands /v1/brands/{id}
reelwire_delete_brand	Hides a brand.		/v1/brands/{id}/delete
reelwire_delete_brand_asset	Clears one slot on a brand: its logo, its logo for dark surfaces, its mark, a stinger, intro or outro, its sound, a typeface.		/v1/brands/{id}/assets/{slot}/delete
reelwire_draft_brand	Answers with a complete, valid style object to start from, rather than an empty one somebody has to learn the shape of: the whole shape a brand's style takes, with Reelwire's own colours and type in it.		/v1/brands/draft
reelwire_duplicate_brand	Makes a second brand like this one under a new name: its colours and type, names and legal line, post text, every language and every file.		/v1/brands/{id}/duplicate
reelwire_list_brands	The brands this workspace has, one short line each: id, name, whether it is on, the title it draws, its logo's ref and how many channels wear it.	Yes	/v1/brands/watches/outlook /v1/brands/watches /v1/brands
reelwire_read_website	Reads one public web page, the business's own website that the person gave you, and answers with what a brand is made of: logo candidates as addresses (bring one into the library with reelwire_import_media, then reelwire_set_brand_asset), whether the logo is drawn inline and has to be asked for as a file, the colours its styles use most (neutrals apart), the typefaces it names, its social profiles (listed, not read: ask for screenshots of those), the pictures on the page, the site's own pages it links to, the most telling first, so that you can read on with another call, and the business as it describes itself: name, kind, telephone, address, opening hours, menu, headings, first paragraphs.	Yes	/v1/brands/read-website
reelwire_set_brand_asset	Points one of a brand's file slots at a file in the media library: the logo, the logo for dark surfaces, the mark, the badge, a background picture or video for one shape or a universal one, the soundtrack, a stinger, intro or outro clip for one shape or a universal one, or a typeface.	Yes	/v1/brands/{id}/assets/{slot} /v1/brands/{id}/assets/{slot}/link
reelwire_update_brand	Renames a brand, turns it off, changes the style a clip wears, or makes, changes or removes a frequency watch over brands.	Yes	/v1/brands/watches/{watchId}/delete /v1/brands/watches/{watchId} /v1/brands/watches /v1/brands/{id}

Channels

Needs Channels.

Tool	What it does	At /mcp	API equivalent
reelwire_create_channel	A channel is one place posts go: one account, in one format (a platform and shape), one language, wearing one brand.	Yes	/v1/channels
reelwire_delete_channel	Stops a channel and takes it off the screens.		/v1/channels/{id}/delete
reelwire_duplicate_channel	Makes a second channel like this one under a new name: its format and shape, language, brand, approval, posting settings, how its posts are handed over by email and webhook, and every source it listens to.		/v1/channels/{id}/duplicate
reelwire_getting_started	SETTING UP, OR CHANGING WHAT IS SET UP.	Yes	/v1/whoami /v1/quick-start/profile/forget /v1/quick-start/profile /v1/quick-start /v1/channels /v1/queues /v1/licence /v1/brands /v1/pocket /v1/brands/watches /v1/brands/{id} /v1/feeds /v1/direct-export/videos
reelwire_list_channels	Where posts go: one channel per platform account and language, each wearing one brand and listening to its own sources.	Yes	/v1/channels
reelwire_list_surfaces	Every surface a channel can publish to (Instagram Reels, TikTok, YouTube Shorts and the rest) with the shapes each takes, and platforms: the dashboard's Platform dropdown, each platform with its shapes, the surface each shape is saved as, and whether Reelwire can post there itself through a platform connector (available) or will later (planned).	Yes	/v1/channels/surfaces
reelwire_stop_everything	Whether the whole workspace is held, and holding it: while it is stopped, or a planned silence covers now, every channel counts as paused, no new post is made and nothing goes out but deletes.		/v1/channels/stop /v1/channels/stop/resume /v1/channels/silences /v1/channels/silences/{id} /v1/channels/silences/{id}/delete
reelwire_subscribe_channel	Subscribes one channel to one source, which is what makes it publish anything at all: a channel with no subscriptions renders nothing, whatever arrives.	Yes	/v1/channels/{id}/subscriptions
reelwire_test_channel_connector	Asks the channel's platform whether the credentials saved on the channel's platform connector still work, and posts nothing: like a ping, it only reads what they reach (the bot and its chat on Telegram, the app and its channel on Slack, the webhook on Discord, the member on LinkedIn).		/v1/channels/connector/test
reelwire_unsubscribe_channel	Removes one subscription.	Yes	/v1/channels/{id}/subscriptions/{subId}/delete
reelwire_update_channel	Changes a channel that already exists: rename it, move it to another brand, change its language or format (surface), turn it off, change how its posts go out (by email, by webhook, by its platform connector, in any mix), or make it ask for approval before anything goes out.	Yes	/v1/compliance/approval-rules/{channelId} /v1/channels/connector/connect /v1/channels/connector/connect/{id} /v1/channels/{id}
reelwire_update_subscription	Changes one subscription: turn it off without losing it, pin it to a cut of the template, pin it to an exact version, or set when a ready-made feed's updates go out on this channel (releaseSchedule: days, or a monthDay, and times in its timeZone (UTC where left out, so give the person's own zone), or delayMinutes after each arrival; null for Send on arrival, as soon as they arrive).		/v1/channels/{id}/subscriptions/{subId}
reelwire_whoami	The workspace this server is connected to, the permissions its API key holds (each in the words a refusal uses, such as "Activity - What went out: write"), which version of Reelwire this is, whom at Reelwire this workspace can reach where somebody looks after it (assignedContact), and WHETHER THE WORKSPACE IS SILENT (silent): Stop everything pressed, or a planned silence on now, holds every channel, so nothing new is made and nothing goes out but deletes until it is resumed (reelwire_stop_everything) or the silence ends.	Yes	/v1/whoami /v1/version /v1/channels/stop

Syndication

Needs Syndication.

Tool	What it does	At /mcp	API equivalent
reelwire_add_subscriber	Adds a participant to a group on the workspace's behalf, as they would subscribe in its iframe: the channels (where the group has several), an email address and/or a webhook as the group allows, and optionally the workspace's own participant ID for them.		/v1/syndication/groups/{id}/partners
reelwire_add_syndication_group	Adds a group, such as one channel for one page, all your channels for everybody, or one language's, with a page of its own.		/v1/syndication/groups
reelwire_list_partner_deliveries	Every email (EMAIL) and webhook call (WEBHOOK) to a participant, newest first, a page at a time: the participant, what it was (post.publish, post.update, post.delete), the channels, its state (DELIVERED, RETRYING, DEAD after the last retry, SKIPPED where the way was gone by the time it was due), where it went and what came back.		/v1/syndication/deliveries
reelwire_list_partners	Every participant, newest first, a page at a time: how they are known (label: the workspace's own id for them where its portal signed one into the page or it typed one, customerId, else their address or their webhook's host), whether they signed up themselves or the workspace added them (source: self or owner), whether they are blocked, their group, the channels they take of it (feeds), their confirmed address and any address waiting for confirmation, their webhook (address, and whether it has answered a test call, without which it receives nothing; its calls are signed with the group's secret, shown only on the group's page), whether they are paused, whether they can receive anything yet (reachable), and their last delivery.		/v1/syndication/partners/{id} /v1/syndication/partners
reelwire_list_syndication_groups	Every syndication group, in its order (or one, by groupId): its name (the workspace's own, never shown to participants), its page title (pageTitle, the heading of its page, null for the usual one), its description (what participants read at the top of its page), its channels (offered to participants to choose from; a group of one channel hands that one to everybody), how it hands posts over (byEmail, byWebhook), the sites allowed to show it (allowedOrigins, empty for any), whether its page shows the logo and title on top (showHeader), the language its participants receive everything in (language: en, de or es), its page's address and the iframe code to put in the portal (page.url, page.frame), its portal key (portalKey: the workspace's server signs a participant's ID or email address with it, ?participant=<id>&sig_participant=<HMAC-SHA256 of the id, hex> and/or &email=<address>&sig_email=<HMAC-SHA256 of the address, hex>, so the page shows them what they subscribed with; never put it in a browser), and how many participants it has (partners), signed up on its page or added by the workspace.		/v1/syndication/groups/{id} /v1/syndication/groups
reelwire_remove_partner	Removes a participant for good: nothing more is handed on to them, and their lines leave the log.		/v1/syndication/partners/{id}/delete
reelwire_remove_syndication_group	Removes a group, its page, and its participants, however they joined: nothing more is handed on to them, and their lines leave the log.		/v1/syndication/groups/{id}/delete
reelwire_resend_to_partner	Sends one line of the participants' log again, from its first attempt: an email with a fresh post kit link, or a webhook call with its clip links signed afresh.		/v1/syndication/deliveries/{id}/redeliver
reelwire_set_syndication_look	Saves any of the syndication settings; a field left out stays as it is, and null puts it back to its default.		/v1/syndication/settings
reelwire_syndication_preview	Draws what a participant sees, in the saved branding with anything in draft laid over it unsaved, and answers its HTML (an email's logo inline, with its subject and sender).		/v1/syndication/preview
reelwire_syndication_settings	The workspace's syndication settings: the branding of everything a participant sees, every group's iframe, email and post kit (logo, title, footer, and four colours: background, card, accent for buttons and links, signature for the title and headings); the email settings (sender: the name, the reply-to address, and mode, either reelwire, from local@ Reelwire's sending domain through Reelwire's mail service, an address no mailbox stands behind, or smtp, through the workspace's own mail server, whose host, port, security, user name and address to send from are in smtp, with password only saying whether one is kept); what each comes to with the defaults filled in (effective); and how many participants the plan holds (partners: those who can receive anything, and the most).		/v1/syndication/settings
reelwire_syndication_test_email	Sends one test email in the branding, the way the emails to participants go: the saved email settings, with anything in draft laid over them unsaved, so a mail server's settings can be tried before they are saved.		/v1/syndication/sender/test
reelwire_update_partner	Changes one participant's settings, only those given: pauses or resumes them (paused, nothing is handed on and nothing waits for later), blocks or unblocks them (blocked, nothing is sent and the same address, webhook or participant ID cannot subscribe in the group again), and sets their participant ID, their channels, their email address or their webhook.		/v1/syndication/partners/{id}
reelwire_update_syndication_group	Renames a group, changes its page title, its description, its channels (the whole list, replacing it) or how it hands posts over, or moves it in the list (position, from 0).		/v1/syndication/groups/{id}

Content sources

Ready-made feeds

Needs Ready-made feeds.

Tool	What it does	At /mcp	API equivalent
reelwire_feed_reference	A shipped feed's preview videos, so you can show what the customer would get before turning anything on.	Yes	/v1/feeds/{feedId}/reference/{ratio}/still /v1/feeds/{feedId}/still/{ratio} /v1/feeds/{feedId}/reference/{ratio} /v1/feeds/{feedId}/reference
reelwire_list_feeds	The ready-made feeds this workspace is offered, one row each and a page at a time, found by market (one industry's feeds: brokers for Finance, tech, public, realestate, pharmacies, others), type, usable, plan (feeds that plan may add), listening (feeds a channel of this workspace listens to), schedule (how often it fires), language (feeds that can be delivered in it) and q (words of a name, title or description), the filters of the dashboard's Ready-made feeds: every feed the industries its owner chose reach, plus any a channel of it still listens to (offered false).	Yes	/v1/feeds
reelwire_set_feed	Switches one format of one ready-made feed off for the whole workspace, or back on.		/v1/feeds

Post composer

Needs Post composer.

Tool	What it does	At /mcp	API equivalent
reelwire_create_post_list	A post list is the third way content arrives: somebody writes it.	Yes	/v1/queues
reelwire_delete_post_list	The list and every post waiting in it are gone for good.		/v1/queues/{id}/delete
reelwire_delete_scheduled_post	One post out of a list.		/v1/queues/{id}/packages/{packageId}/delete
reelwire_list_post_lists	The lists of posts written by hand, each holding posts that go out at their own time, with its posts in the order they go out (a post's id is what reelwire_update_scheduled_post and reelwire_delete_scheduled_post take) and how far each got.	Yes	/v1/queues
reelwire_plan_posts	THE NUMBERS BEHIND A CONTENT PLAN, before anything is written: for one post list, the times posts can go out over the next weeks (up to 13), in the audience's time zone and in UTC, between 06:00 and 20:00 there, as many as the month's allowance pays for once every channel listening renders each post and what the channels already post is counted, and never more a day than a channel's ramp allows (1 a day in its first week, 2 in weeks two and three, 3 from week four).	Yes	/v1/queues /v1/queues/{id}/plan /v1/templates /v1/channels /v1/quick-start/profile /v1/brands/{id} /v1/templates/{templateId}/validate
reelwire_schedule_post	Adds a post to a post list, to go out at the time given, or with posts a whole plan of up to a hundred at once, all written or none (every one is checked first, and a refusal names each post that does not fit by its number, /posts/3/...).	Yes	/v1/queues/{id}/packages/batch /v1/queues/{id}/packages
reelwire_update_post_list	Renames a post list or turns it off.		/v1/queues/{id}
reelwire_update_scheduled_post	Edits a post that is still waiting in a list: its title, its content, the template, cut or build it is drawn with, or when it goes; or cancels it.	Yes	/v1/queues/{id}/packages/{packageId}

Reelwire Pocket

Needs Reelwire Pocket.

Tool	What it does	At /mcp	API equivalent
reelwire_pocket	Reelwire Pocket is a content source made of things somebody does: on a connected device they press one of its actions, a big button such as Visiting a property, add photos, videos and a few notes, and look at three to five stills before the clip goes out.	Yes	/v1/pocket/clips /v1/pocket/{id}/clips/{clipId} /v1/pocket /v1/pocket/{id}/clips
reelwire_update_pocket	Makes a pocket or changes its settings; a field left out stays as it is.	Yes	/v1/pocket/order /v1/pocket /v1/pocket/{id} /v1/pocket/{id}/pair /v1/pocket/{id}/devices/{deviceId}/delete /v1/pocket/{id}/devices/{deviceId} /v1/pocket/{id}/interview /v1/pocket/{id}/clips /v1/pocket/{id}/clips/{clipId}/change /v1/pocket/{id}/clips/{clipId}/text /v1/pocket/{id}/delete /v1/pocket/{id}/clips/{clipId}/preview /v1/pocket/{id}/clips/{clipId}/post /v1/pocket/{id}/clips/{clipId}/discard /v1/pocket/{id}/clips/{clipId}/archive /v1/pocket/{id}/clips/{clipId}/unarchive

Custom feeds

Needs Custom feeds.

Tool	What it does	At /mcp	API equivalent
reelwire_create_stream	A stream is where a workspace's own systems push events: it has an id to name in the event body and one template every event it carries is drawn with.		/v1/streams
reelwire_delete_stream	The stream stops accepting data: anything still sending its id gets a refusal saying it was removed, rather than silence.		/v1/streams/{id}/delete
reelwire_list_streams	The custom feeds (streams) this workspace's own systems send events to.		/v1/streams /v1/stream
reelwire_suggest_field_map	Reads the last event this stream received and proposes a map from that shape to the template's fields, handing back the proposal, the template's own fields and the sample so it can be checked before anybody saves it.		/v1/streams/{id}/suggest-map
reelwire_update_stream	Changes a stream's name, description, whether it is on, the template it draws with, or its field map.		/v1/streams/{id}/update

Custom feeds - Send raw data

Needs Custom feeds - Send raw data (write only).

Tool	What it does	At /mcp	API equivalent
reelwire_send_event	Push something that happened into a stream.		/v1/streams/{id}/test /v1/stream
reelwire_send_feed_event	Sends one event to a feed Reelwire carries, as a producer would.		/v1/ingest/{source}/{format}
reelwire_validate_event	Takes exactly what reelwire_send_event takes and answers whether it would have worked, creating nothing.		/v1/stream/validate
reelwire_validate_feed_event	Takes exactly what reelwire_send_feed_event takes and answers whether it would be accepted, naming the field and the reason when it would not.		/v1/ingest/{source}/{format}/validate

Connections

Webhook

Needs Webhook.

Tool	What it does	At /mcp	API equivalent
reelwire_set_webhook	Sets the URL Reelwire hands posts over to, for every channel with Webhook switched on.		/v1/webhook
reelwire_test_webhook	Sends one signed ping to the workspace's webhook address now, exactly as a hand-over arrives (the same headers and signature, about no post), and answers what came back: whether it got through, the status, how long it took and the start of the receiver's answer.		/v1/webhook/test
reelwire_webhook	The workspace's webhook: the URL Reelwire calls with every hand-over of a channel that has Webhook switched on (one signed call per hand-over, carrying every channel of the batch), whether it is on, and a hint of the signing secret, which is all a receiver needs to check a delivery.		/v1/webhook

Activity

Needs Activity, which is read only.

Tool	What it does	At /mcp	API equivalent
reelwire_list_ingest_events	The received log: every event that reached this workspace, newest first, from a shipped feed, from its own API streams or from a post written by hand, with what became of it.		/v1/ingest-events/{id} /v1/ingest-events

Activity - What went out

Needs Activity - What went out.

Tool	What it does	At /mcp	API equivalent
reelwire_list_deliveries	The delivery log: every way every hand-over went out, newest first, one line for its email (mechanism EMAIL), one for its webhook call (WEBHOOK) and one per post for its platform connector (CONNECTOR), each with the channels it carried, its state, the attempt it is on, the status code that came back and the error.		/v1/deliveries/{id} /v1/deliveries
reelwire_redeliver	Sends one line of the delivery log again, now rather than at its next retry: a webhook call with the same delivery id and its clip links signed afresh, or the same email again.		/v1/deliveries/{id}/redeliver

My account

Team

Needs Team.

Tool	What it does	At /mcp	API equivalent
reelwire_invite_teammate	Creates the person with the powers you name and emails them a link to choose their password.		/v1/compliance/auditors/{userId}/resend /v1/compliance/auditors /v1/team/users
reelwire_list_team	Who is in the workspace, what each of them may do, whether they have signed in yet, and how many more people the plan allows.		/v1/compliance/auditors /v1/team/users
reelwire_remove_teammate	Ends their access at once: any session they have is dead on the next request.		/v1/compliance/auditors/{userId}/delete /v1/team/users/{userId}/delete
reelwire_resend_invite	For the colleague whose setup email went to spam or was lost.		/v1/team/users/{userId}/resend
reelwire_update_teammate	Changes somebody's powers or the name beside them.		/v1/team/users/{userId}

Subscription

Allowance

Needs Allowance, which is read only.

Tool	What it does	At /mcp	API equivalent
reelwire_render_quota	How many renders the month's allowance has left, how much storage is used, and how that storage is split between the media library and rendered clips, with the seats (seats: colleagues besides the owner) and syndication participants (partners: those who can receive something) in use against the most the plan holds.	Yes	/v1/renders/quota

Plan

Needs Plan, which is read only.

Tool	What it does	At /mcp	API equivalent
reelwire_plan	The plan, what it switches on, how many people and syndication participants it allows, and what the next tier up would add.	Yes	/v1/licence

Not an API call

These answer from the server itself: the documentation it carries, who the key belongs to, the way to the tools a list leaves out, and the one act it has to refuse.

Tool	What it does	At /mcp
reelwire_commission	The owner's own affiliate programme: their link and promo code, how much they have earned, what is held and what they can collect, the customers they brought by number, their tax details and their agreement.
reelwire_find_tools	This connection lists the everyday tools; more are here than it shows, by job: syndication (groups of channels handed on to participants), the compliance record and the audit log (Enterprise), custom feeds and events, the webhook and the delivery log, the team, and less common work on posts, brands, channels, sources, videos and media.	Yes
reelwire_media_upload_page	Answers with the address of the dashboard's Media screen, where the person uploads pictures, videos, sound and fonts from their own computer into the library themselves.	Yes
reelwire_my_account	Reads, and changes where told, what belongs to the person who connected this assistant: the name they go by, the language they read Reelwire and its emails in, their time zone, whether they get Reelwire's optional emails, and the workspace's industries, which decide what ready-made feeds and templates it is offered.
reelwire_read_doc	Read a documentation page in full, by the path a search result gave, such as /manuals/api/events/ or /manuals/dashboard/brands/.	Yes
reelwire_resend_post	SENDS AGAIN, the one way named, as the post reads now; the post's state does not change.	Yes
reelwire_search_docs	Search the manual, the API reference and the MCP guide.	Yes
reelwire_use_tool	Runs one tool reelwire_find_tools found, by its name, with its arguments, exactly as calling it directly would: the same check of the arguments, the same permissions, the same answer.	Yes