lmnts

Search this client's posts by title/content keyword, status, and/or scheduled date, to find the real post id behind a natural-language reference like "the August 1st draft" or "the Fieldpiece post." Always use this before update_post_fields/attach_asset_to_post/etc. when the user refers to a post by description rather than giving you an id directly. Never guess an id. For "what went live", do not filter on published: that status is transient and a live post moves on to notified within a minute or two, so it matches almost nothing. Search each of published, notified, notification_error instead, or leave status off and read what comes back.

find_posts

Search this client's tasks by title/content keyword, status, and/or due date, to find the real task id behind a natural-language reference like "the logo task" or "what's due Friday." Always use this before update_task_fields/update_task_status/etc. when the user refers to a task by description rather than giving you an id directly: never guess an id.

find_tasks

Step two of two for a large local file: call this with the storage_path start_asset_upload returned, once your PUT of the bytes has come back 200. It reads the real type from the file's first bytes, refuses and deletes anything that is not an image or a video, adds it to the client's asset library, and returns the asset id you then hand to attach_asset_to_post or attach_asset_to_task. Calling it twice for the same storage_path returns the same asset instead of a second copy. Videos get poster frames a few minutes later on their own.

finish_asset_upload

Generate a social media graphic or promotional image and save it to this client's asset library. Only call this when the user explicitly asks for an image/graphic to be created: not for general conversation. The image provider has already been chosen by the user outside this conversation; you do not choose it.

generate_image

Read a client's brand knowledge: the brand profile lmnts has learned from their published work, plus the documents and links their team has added to the client's knowledge base (brand guides, tone of voice, product information). Read this before writing copy or planning a calendar for a client, so the work sounds like them rather than generic. Long knowledge bases are trimmed to the same character budget the app itself uses, and the item list says which pieces are still being extracted and so are not in the text yet. Read only.

get_client_knowledge

Read one post in full: title, content, YouTube title, approval and pipeline status, whether it is in review, each platform with its own scheduled time, status and per-platform options (Instagram format, TikTok settings, Threads reply control, YouTube audience, Pinterest board, title, link and alt text, Reddit title and post type), every attached asset with a one-hour signed URL (and a poster frame plus processing status for videos), and the copy limits its platforms impose. Use it to check a post before editing, scheduling, or describing it to the user. An Instagram row whose instagram_format is 'story' publishes no caption at all, so say so rather than reading the post's copy back as what will appear. Use find_posts first when you only have a description, not an id.

get_post

Read how a client's published posts actually performed: likes, comments, shares, saves, reach, impressions, video views and clicks for each platform a post went out on, newest numbers first. Use it before planning a calendar so the plan is based on what worked, and to answer questions like 'what did best last month'. Covers only posts that are already live in the window you ask for; a draft or scheduled post has no numbers yet. Numbers are the last snapshot lmnts captured from each platform, so they can trail the platform's own dashboard by a few hours, and a platform that reports no value for a metric comes back null rather than zero. Organic performance only: this tool does not expose ad spend, paid reach or ROAS. Default window is the last 30 days.

get_post_performance

Read one task in full: its title and details, status, due date and start date, who it is assigned to, which brand it belongs to, and every attached file with a one-hour signed URL and the attachment id remove_task_asset takes. Use it before editing a task or describing it to the user, and use find_tasks first when you only have a description rather than an id. The comment thread is not included; read it with list_task_comments.

get_task

List a client's asset library (Brand files: logos, photos, videos) newest first, each with its id, type, and a one-hour signed URL you can view or share; videos also get a poster frame URL. Use an asset id from here with attach_asset_to_post or attach_asset_to_task. Paginated: default 25, use offset for more.

list_assets

List the lmnts clients (agency customers) you can work with, with each one's id, brands, and connected social platforms. Call this first to find the client_id the other tools need, or to check what a client has connected before choosing platforms. Paginated: default 25 per page, use offset for the next page.

list_clients

List the social platforms a client (or one of its brands) has connected, which is the exact set a post may target. Use it before create_post or add_post_platform when you are unsure what is connected. A result of just "other" means nothing is connected and posts will be published by hand.

list_connected_platforms

Read the comment thread on a post, oldest first. This is where a post's feedback lives, so read it before acting on an instruction like 'make the changes the client asked for': a comment marked changes requested is the note left by a Request changes decision. Each comment's id is what add_post_comment takes as parent_comment_id to reply in the same thread. Attachment contents are not returned, only whether a comment carries any.

list_post_comments

Read the comment thread on a task, oldest first. Same shape as list_post_comments: a comment marked changes requested is the note left by a Request changes decision, and each id can be replied to with add_task_comment.

list_task_comments

Submit a post for review. Requires the post to already have content, at least one platform with a scheduled time, and at least one attached asset: if any of those are missing, this will fail with a clear message about what's needed; relay that to the user rather than retrying blindly.

mark_post_ready_for_review

Submit a task for review, which notifies the client team that there is something to look at. The task needs details (its content) first; if it has none this fails with a message saying so, which is worth relaying rather than retrying. Use this for both a first submission and a resubmission after changes were requested.

mark_task_ready_for_review

Remove one attached file from a draft post. This is the other half of attach_asset_to_post: to replace an attachment, attach the new file and then remove the old one with this, or the post keeps both and platforms such as LinkedIn and Instagram refuse it. The file is moved to the trash, not erased: the team can restore it in lmnts for 30 days, after which it is purged, so tell the user it was removed and is recoverable rather than calling it permanent. asset_id is the id of the file as it is attached to this post, not the client_assets id that was passed to attach_asset_to_post; when the id does not match, the refusal lists what is attached with the right ids. Only works on a draft that has not been submitted for review.

remove_post_asset

Remove a platform from a draft post that has not been submitted for review. Use it when the user changes their mind about where a post goes. Calling it for a platform that is not on the post is harmless.

remove_post_platform

Remove one attached file from a task. This is the other half of attach_asset_to_task: to replace an attachment, attach the new file and then remove the old one with this. The file is moved to the trash, not erased: the team can restore it in lmnts for 30 days, after which it is purged, so tell the user it was removed and is recoverable rather than calling it permanent. asset_id is the id of the file as it is attached to this task, which get_task lists, not the client_assets id that was passed to attach_asset_to_task; when the id does not match, the refusal lists what is attached with the right ids. Refused once a task is in review or completed.

remove_task_asset

Request changes on a post that's pending review, with a note explaining what needs to change.

request_post_changes

Send a task in review back to whoever is working on it, with a note saying what needs to change. The note is posted as a comment on the task (flagged as a change request) and emailed and pushed to its assignees, so write it for them and be specific.

request_task_changes

Move a post that is already scheduled to a new date and time, and leave it scheduled. This is the only way back from schedule_post: it pulls the post off the platforms (cancelling the schedules they are holding), sets the new date and time, and schedules it again, keeping its approval so no second review round is needed. Pass platform to retime one platform row and leave the others where they are. The post must currently be scheduled; use set_post_schedule for a draft. The new time must be in the future, because a past time would publish the post immediately. If the final re-schedule step fails the post is left as an approved draft at the new time and the reply says so, so read the reply rather than assuming the post is still live on the calendar. Dates and times are America/New_York wall clock, the same as the lmnts calendar.

reschedule_post

Commit an approved post to its connected platforms so it publishes at its scheduled time (or right away if that time has passed). Approving a post already schedules it, so this is for retrying a post that failed to schedule, or one approved before approval started scheduling. Requires the approve-and-publish permission and a post whose approval status is approved. If the scheduled time has already passed this refuses and asks for confirmation: only call again with confirmed_past_due=true after the user has explicitly agreed to publish it immediately. Use set_post_schedule to move the time instead.

schedule_post

Set the per-post options one platform takes on a draft post: Instagram's format (a feed post, or a Story) and whether a Reel also shows in the profile grid; TikTok's visibility, comment/duet/stitch and commercial-content disclosure; Threads' reply control; YouTube's made-for-kids audience; Pinterest's board (required to schedule, by name), title, destination link and alt text; Reddit's title, post type, link and NSFW/spoiler flags. Only instagram, facebook, tiktok, threads, youtube, pinterest and reddit have options; any other platform is refused, as is a field that belongs to a different platform. The platform must already be on the post (add_post_platform puts it there, and takes these same fields). Options left out keep their current value; get_post reports what each platform row currently holds. Only works on a draft that has not been submitted for review. Instagram Story: A story takes exactly one image or one video of 3 to 60 seconds; anything else is refused with the reason. An Instagram story publishes NO caption: Instagram's API has no caption field for stories, so this post's copy stays in lmnts for reference and approval and never appears on the story itself. Say so when you tell the user the story is set, and do not write a caption for it. Reddit: A Reddit post needs its own title (reddit_title, up to 300 characters), separate from the caption, and cannot be scheduled without one. The caption is posted only as the body of a text post; image, video, gallery and link posts carry the title alone. Posts go to the connected account's own profile.

set_platform_options

Set when a draft post goes out. scheduled_date moves the whole post to that day (every platform keeps its own time of day). With scheduled_time and no platform, every platform is set to that time; with a platform, only that platform's time changes, and scheduled_date can then be left off to keep the day the post is already on. Only works on a draft that has not been submitted for review. This sets the plan; it does not publish. Approving the post (approve_post) is what commits it to the platforms. Dates and times are America/New_York wall clock, the same as the lmnts calendar.

set_post_schedule

Step one of two for putting a LARGE local image or video into a client's asset library: the files upload_asset refuses because they are over its 2.5 MB file_base64 limit. It returns a one-time upload URL, and you send the bytes to it yourself, so the file never has to fit inside a tool call. Do exactly this: (1) call this tool with the file's name, (2) make an HTTP PUT to the returned upload_url whose body is the file's raw bytes, with the single header Content-Type set to the returned content_type_header, no Authorization header and no multipart or base64 wrapping, (3) when that PUT returns 200, call finish_asset_upload with the returned storage_path, which checks the file and adds it to the library. The URL works for two hours and for that one file only. If the file is already on the public web at a direct link, upload_asset with source_url is simpler; if it is small, upload_asset with file_base64 is simpler.

start_asset_upload

Update an existing post's internal title, its content, its YouTube video title, and/or which brand it belongs to. Note that 'title' is the internal working title nobody outside the team sees, while 'youtube_title' is the real video title shown on YouTube. They are different things and setting one does not set the other.

update_post_fields

Assign a task to a specific person by their email address (must already be on this client's team). Adds them alongside any existing assignees rather than replacing them.

update_task_assignee

Update an existing task's title, content, due date and/or start date. create_task takes both dates, so this is how they change afterwards: "move the logo task to Friday" is due_date. Dates are YYYY-MM-DD in the agency's timezone; a due date keeps the task's existing time of day.

update_task_fields

Change a task's status: open, in_progress, ready_for_review (shown as In Review) or changes_requested. 'done' (shown as Completed) is deliberately not accepted here, because completing a task goes through review: mark_task_ready_for_review submits it, then approve_task completes it, or request_task_changes sends it back with a note. Prefer mark_task_ready_for_review over setting ready_for_review here, since only that path notifies the client team that there is something to look at. Note: a client-portal user can only keep a task at 'open'; only the agency can move it further, and if that is who is asking, this will tell you so.

update_task_status

Save an image or video into a client's asset library, so it can then be attached to a post or task with attach_asset_to_post or attach_asset_to_task. Three ways in, in order of preference: `file` for a file the user attached in this conversation (ChatGPT fills it in); `source_url` for a direct public https link; `file_base64` for the bytes themselves, when you can read the file but cannot give a link, for files up to 2.5 MB only (for a bigger local file use start_asset_upload and finish_asset_upload instead, which send the bytes straight to storage). Images and videos only, up to 50 MB by URL; the real type is read from the bytes, not from the name or the declared type. Direct links only (no redirects, no private hosts). The same file uploaded twice returns the existing asset rather than a duplicate.

upload_asset

Look at the actual image(s) already attached to a post: use this whenever the user asks what an attachment shows, or wants copy written specifically for the product/person/scene pictured, rather than guessing from the title alone. Video attachments are shown as a few extracted frames instead of the full clip (extracted a few minutes after upload: if a video was just attached, its frames may not be ready yet). Other non-image, non-video files (PDF, etc.) are listed by name but not shown. Shows at most 4 images and 2 videos per call.

view_post_assets

Look at the actual image(s) already attached to a task: use this whenever the user asks what an attachment shows, or wants a description written specifically for the product/person/scene pictured, rather than guessing from the title alone. Video attachments are shown as a few extracted frames instead of the full clip (extracted a few minutes after upload: if a video was just attached, its frames may not be ready yet). Other non-image, non-video files (PDF, etc.) are listed by name but not shown. Shows at most 4 images and 2 videos per call.

view_task_assets