Skip to content

Tool reference

Sharek MCP exposes the tools below. You never call them by name: your assistant picks them, and usually chains several to answer one request. This page is here so you know what is possible, and so you can tell whether a tool failed or your assistant simply did not try.

Tool What it does
integrationList Lists your connected channels
groupList Lists your brands
integrationSchema Reads what a channel type requires before posting
triggerTool Looks up ids a channel needs, like a board or a subreddit
integrationSchedulePostTool Creates and schedules posts
postsListTool Lists your posts between two dates
postSettingsTool Changes the settings of a post that is not published yet
deletePostTool Deletes a post
uploadFromUrlTool Pulls media into your library from a public URL
mediaListTool Lists the media already in your library
uploadWidgetTool Shows an upload box for files on your device
uploadWidgetStatusTool Lists the files uploaded through that box
generateImageTool Generates an image
generateVideoOptions Lists the ways video can be generated
videoFunctionTool Fetches options a video generator needs, like voices
generateVideoTool Starts generating a video
videoStatusTool Checks on a video being generated
ask_sharek Asks the Sharek agent a question

How you connected your tool decides which of these it sees:

  • API key: every tool above.
  • Sign in with Sharek: every tool except ask_sharek.

The upload box appears only in apps that show interactive widgets, such as Claude and ChatGPT. Everywhere else, your assistant adds media from a link instead.

Lists the channels connected to your account: the id your assistant needs for every later call, the channel name, and which platform it is.

Takes an optional group id to narrow the list to one brand. Without it, you get everything.

API equivalent: list channels.

Lists your brands. Useful when you run channels for several brands and want the assistant to work inside one of them. Feed a brand’s id from here into integrationList. The tools keep older names for a brand: group in integrationList and customer in postsListTool.

API equivalent: list brands.

The step that makes the difference between a post that schedules and one that gets rejected. For a given channel type it returns the platform’s rules, its maximum content length, the settings that channel accepts, and the helper tools available for filling those settings in.

Needs the channel identifier and whether the account is premium, which matters on X where premium accounts get longer posts.

API equivalent: get channel rules and settings schema.

Some settings want an id you cannot reasonably know. Which subreddit, which Pinterest board, which Discord channel. integrationSchema says which helper to call, and this tool calls it.

Needs the channel id, the helper name from that schema, and whatever the helper asks for, which is sometimes a search term. If your assistant asks you “which board?” partway through a request, this is why.

On LinkedIn, the helpers include a mention lookup: it finds a company page to tag in the post by the page’s exact vanity name, the part after linkedin.com/company/. LinkedIn is the only channel with this lookup today.

API equivalent: trigger a channel tool.

The one that actually creates the post. Everything else exists to feed it.

For each channel you are posting to, it takes:

  • The channel id and whether that account is premium.
  • A date, in UTC.
  • A type: draft to park it, schedule to queue it, or now to publish immediately.
  • The content, as a list where the first item is the post and every item after it is a comment or the next part of a thread.
  • The media on each item of that list. Each attachment is the address of media Sharek hosts, or an object with that address as path plus optional alt text in alt. For a video, the object can also set the cover: thumbnail, the address of an uploaded JPEG or PNG, or thumbnailTimestamp, the frame to use, in milliseconds.
  • The settings that integrationSchema said this channel needs.
  • Whether to shorten links in the content.

Content is HTML, not plain text. Each line is wrapped in <p>, and the tags allowed are p, h1, h2, h3, ul, li, strong and u, plus img on platforms whose rules put pictures inside the text, and span only for a mention, written exactly as the mention lookup returns it. Bold and underline cannot be combined on the same text. Your assistant handles this; it matters only when you are wondering why formatting came out differently from what you typed.

One call can carry many posts. Twenty posts to Facebook across twenty days is one call with twenty entries, not twenty calls. Each post comes back with a preview link you can open.

This tool only creates posts. Changing or deleting one goes through the tools in the next section.

API equivalent: create a post.

Lists every post between two dates, whatever its state: scheduled, draft, published or failed. Needs a start and an end date in UTC, and takes an optional brand id to narrow it to one brand. Each post comes back with its id, publish date, state, any error, its content, its channel and its current settings.

To see everything coming up, your assistant passes a wide window, such as the year ahead. The ids it gets here are what the next two tools need.

API equivalent: list posts.

Changes the platform settings of a post that is not published yet, scheduled or draft, such as who can reply on X. The text and the date stay exactly as they are.

Needs the post id and only the settings to change. Anything it does not pass stays as it was. Which settings exist comes from integrationSchema.

API equivalent: update post settings.

Deletes one post on one channel, together with its comments. Needs the post id.

  • A post you created for several channels has a separate id on each one, so deleting it on one channel leaves the others.
  • A repeating post is deleted with every repetition.
  • A deleted scheduled post is never published.
  • Deleting a post that is already published removes it from Sharek only. It stays live on the social network.

A deletion cannot be undone.

API equivalent: delete a post.

Pulls an image or video from a public URL into your media library and returns the stored copy.

This is not an optimization. Attachments must be hosted by Sharek, so media from anywhere else has to come through here before it can go on a post. If you hand your assistant a link to an image, this is the tool that makes it usable. Files on your own computer cannot come through a link: use the upload box below, the Sharek CLI or the public API.

API equivalent: upload from a URL.

Lists the images and videos already in your media library, newest first, 32 at a time, and can search them by file name. Your assistant attaches one of these directly instead of uploading it again.

API equivalent: list media.

Shows an upload box in the conversation, so you can add images and videos from your own device: images up to 10 MB and videos up to 1024 MB. What you upload lands in your media library and is reported back to your assistant, ready to attach.

The box appears only in apps that show interactive widgets, such as Claude and ChatGPT. To get an upload ticket, the box itself calls uploadWidgetTicketTool, a tool meant for the box alone: apps that show the box keep it from your assistant, and other apps may list it, though your assistant has no reason to call it.

API equivalent: none, as the box has no public route. The closest is upload a file, which sends a file from your device over HTTP.

Lists the files uploaded through one upload box. A file marked processing is still being prepared: ask again in a moment. It does not list the rest of your library; that is mediaListTool.

API equivalent: none. The public API has no route for this.

Generates an image from a prompt and puts it in your media library, ready to attach. Returns the stored media, or an error when your image credits are exhausted.

API equivalent: none. The public API has no route for this.

Lists the video generators available to you. Each one describes what it produces and what it suits, so the assistant can pick deliberately and tell you why. The generators are the same ones the composer offers, described in full under AI images and video.

API equivalent: none. The public API has no route for this.

Some generators need a choice made before they run, a voice being the common one. This fetches the available values for that choice.

API equivalent: video provider functions.

Starts generating the video and returns a job id, or an error when your video credits are exhausted or the video type is not available during your trial. Generating takes minutes, so your assistant does not wait: the finished video appears in your media library.

API equivalent: generate a video.

Checks on a video started with generateVideoTool, using its job id. Your assistant calls it when you ask about the video later. Once it is done, the result carries the video’s link, ready to attach to a post.

API equivalent: none. The public API has no route for this.

Puts a question to the Sharek agent, which answers by using the tools on this page with your account. It has the same scheduling, media and video tools as Samy in the app, and none of Samy’s chat-only abilities: it does not read the web, use your brand kits, or make images from images you attach. Useful when the question is about content or strategy rather than a specific action. Only connections that use an API key have it.

API equivalent: none. The public API has no route for this.

  • Credits exhausted on image or video generation returns an error rather than stopping the conversation. Everything else in the request still works.
  • A rejected post is nearly always a missing or wrong setting for that platform. The fix is another look at integrationSchema.
  • A post that cannot be changed or deleted comes back with an error saying why, for example a settings change on a post that is already published.
  • No channels listed means the account has none connected, not that the tool broke. Connect one first.

Posting, channels, media and starting a video also work over HTTP: see the public API. Image generation, the upload box, generateVideoOptions, videoStatusTool and ask_sharek have no public route.