# Can Claude Cowork turn a nature reserve's field notes into weekly Mastodon posts? > Source: https://tareno.co/agents/claude-cowork/mastodon > Language: en > Last reviewed: 2026-10-24 > 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. ## Connection facts | Field | Value | | --- | --- | | Product surface | Claude Cowork (claude-plugin:claude-cowork) | | Available connection | Published plugin | | Connection evidence | tested | | Methods | plugin, mcp | | Authentication | oauth | | Setup | [Setup guide](https://tareno.co/docs/mcp) | | Install or connect | [Open setup](https://tareno.co/docs/mcp) | | Evidence observed | 2026-10-21 | | Facts reviewed | 2026-10-25 | Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface. Agent: Claude Cowork · Network: Mastodon · Hub: [Claude Cowork and Tareno](https://tareno.co/agents/claude-cowork) ## Short answer **Can Claude Cowork turn field notes and photos into Mastodon posts for a nature reserve?** 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. 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. ## Example: a wetland reserve posts three observations a week 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. ## Step by step 1. **Share the notes and the photos.** 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. 2. **Choose three observations.** 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. 3. **Strip sensitive locations.** 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. 4. **Write the posts and descriptions.** 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. 5. **Save the drafts.** 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. 6. **Space the requests and approve.** 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. ## Prompts to copy ### Pick the observations ```text 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. ``` ### Write posts and descriptions ```text 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. ``` ### Check species and counts ```text 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. ``` ### Save the drafts ```text 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. ``` ## Mastodon in Tareno - Tareno's configuration for Mastodon allows up to four images with a description each, and the Mastodon community expects descriptions, which suits a photo-based nature account. - Mastodon's documentation says character limits and media limits are set per server, with 500 characters and four attachments as the example, so check your own server. - Tareno gives links an automatic preview on Mastodon, so a post can link to the reserve's visitor information. - Tareno does not read posts or replies on Mastodon, so the ranger reads questions in the app and answers there. Official rules ([Mastodon documentation: statuses and instance configuration](https://docs.joinmastodon.org/methods/statuses/), checked 2026-10-24): - Character and media limits are set by each server, not by Mastodon itself. The documentation's example server allows 500 characters and 4 attachments, and counts every link as 23 characters. - A scheduled status must lie at least 5 minutes in the future, and a poll cannot be combined with media attachments. - Visibility can be public, unlisted, private (followers only) or direct, and a content warning can be set with spoiler text. ## Mistakes to avoid - Publishing a nest site. Name the reserve, not the spot. - Posting every sighting. Three a week is a rhythm followers can keep up with. - Trusting descriptions written without seeing the photo. Compare each. - Counting from a note written in a hurry. Check counts against the original entry. ## What does not work - Claude Cowork cannot see the photos, so it writes descriptions from your notes and you check each against the image. - It cannot judge which locations are sensitive for a species, so the ranger decides what stays out. - It cannot publish a post on its own, since a time request becomes a post only after you approve it in the Tareno dashboard. ## Frequently asked questions ### How does Cowork avoid revealing a nest site? 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. ### Can Cowork identify species from photos? 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. ### How many posts a week? 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. ### Are image descriptions required? 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. ### What if our server has a smaller limit than 500 characters? 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. ### Will the posts go live without my approval? 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. ## Tareno tools used - `list_media` - `list_accounts` - `create_drafts` - `get_action_status` Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them. ## Related - [Claude Cowork × Tareno overview](https://tareno.co/agents/claude-cowork) - [Media library](https://tareno.co/features/media-library) - [Post scheduling](https://tareno.co/features/post-scheduling) - [Approval workflows](https://tareno.co/features/approval-workflows)