Loading...
×Share a week of field notes and photos with Claude Cowork; it writes Mastodon posts with image descriptions, leaves out sensitive locations and saves drafts in Tareno for your approval.
Yes. Claude Cowork reads the week's notes in a shared folder, picks three observations worth sharing, writes posts with image descriptions, leaves out locations of sensitive species and saves drafts through Tareno. A ranger checks species and counts. Scheduling stays pending until you approve it in Tareno.
Last reviewed 2026-10-24 · Markdown version for AI agents
Nature reserves and wildlife trusts have rangers who write everything down and almost no time to post. Their notes hold the best content: the first swallows of the year, a fox den found on the western edge, the water level in the pond. Mastodon is where many naturalists and conservation people are, and its communities value accurate species names and image descriptions. Claude Cowork works on a folder of notes and photos and can turn a week of them into posts. This page follows a small reserve through a weekly routine, with the single most important rule for this subject: sensitive locations stay out.
Imagine a ranger who drops her weekly notes and six photos into a Cowork folder. Cowork reads the notes, picks three observations — the first lapwing chicks, a rising water level and a grass snake sunning — and writes a post for each within 450 characters. It notices that one note gives the exact grid reference of the lapwing nests and leaves it out, using only the name of the reserve. It drafts a description for each photo from her notes, finds the files with list_media, and saves three drafts with create_drafts for the reserve's account. She checks species and counts.
Put the week's notes and the photos in one Cowork task. A short sentence per photo in the notes gives Cowork what it needs to write a description.
Ask for the three most shareable observations with the line of the notes each comes from. A reserve that posts every day trains followers to scroll past.
Tell Cowork to remove grid references, nest sites and anything that could lead a visitor to a vulnerable species. Name the reserve, not the spot.
Request a post per observation within 450 characters and a description per photo, written from your notes, because Cowork cannot see the images. Check each against the photo.
Cowork finds the photos with list_media, confirms the account with list_accounts and saves the drafts through create_drafts. Mastodon servers set their own limits, so check yours.
Give three days and an IANA time zone. Mastodon's documentation requires scheduled posts to be at least 5 minutes ahead; approve each request in the Tareno dashboard.
Read this week's field notes in the shared folder as source for Tareno drafts and choose the three most shareable observations for the public, each with the line of the notes it comes from. Flag every line that contains a grid reference, a nest site or another location I should not publish.For each chosen observation write a Mastodon post within 450 characters and a description for the matching photo, using only my notes and the reserve name as the place. Say clearly that you cannot see the photos, so I will check each description against the image.List every species name and every count in the three posts together with the note it comes from, and mark any name written in two ways or any count that differs between notes. Do not change anything, and tell me what you are unsure about.Use Tareno to find the photos [lapwing-1, water-2, snake-1] in my media library, confirm the reserve's Mastodon account [handle@server] and save the three approved posts as drafts with their photos. Return a table with draft ID and observation, and request no time yet.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: Mastodon documentation: statuses and instance configuration, read on 2026-10-24. Platform rules change; check the page before you rely on a number.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
You tell it which details to remove, and it flags every line with a grid reference or nest location. It cannot know which species are vulnerable, so the ranger reads the posts before approval.
No, and it cannot see them. Species names come from your notes. Cowork reports names written in two ways and counts that differ between notes, so you can correct the record before the post.
Three is a comfortable rhythm for a small reserve. Cowork picks the strongest observations from the notes and tells you which ones it left out, so you can swap one for another.
Not by the software, but the community expects them, and Tareno takes a description per image. Cowork drafts one from your notes, and you correct it against the photo.
Tell Cowork the limit and it shortens each post accordingly. Mastodon's documentation says limits are set per server, so the figure in Tareno's configuration is only an assumption.
No. A scheduling request becomes a pending action in Tareno, and Mastodon receives each post only after you approve it in the dashboard. `get_action_status` shows what happened afterwards.