# Can Cursor draft Facebook posts from your web shop's repository?

> Source: https://tareno.co/agents/cursor/facebook
> Language: en
> Last reviewed: 2026-10-24
> Use Cursor with Tareno to read a shop's product data and release notes, write Facebook Page posts for new items and save them as drafts you approve in Tareno.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Cursor (cursor) |
| Available connection | Available in Cursor Directory |
| Connection evidence | documented |
| Methods | mcp, skill |
| Authentication | oauth |
| Setup | [Setup guide](https://tareno.co/docs/mcp) |
| Install or connect | [Open setup](https://cursor.directory/plugins/tareno) |
| Evidence observed | 2026-10-19 |
| 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: Cursor · Network: Facebook · Hub: [Cursor and Tareno](https://tareno.co/agents/cursor)

## Short answer

**Can Cursor turn our shop's new products and features into Facebook Page drafts?**

Yes. Cursor reads the product data and release notes in your repository, writes a Facebook post for each new item, matches product photos from your Tareno library and saves drafts for your Page. It cannot check live stock unless you tell it, and a scheduling request stays pending until you approve it.

A small web shop adds products and features in the same repository where its developer works all day. The Facebook Page then lags behind, because writing a post means leaving the editor, finding the photo, remembering the price and typing it all again. Cursor is already in the repository, so it can read the product data, the changelog and the descriptions, and write posts that match. Tareno saves the result as drafts on the Page. This page follows a one-developer shop through a product launch, including what Cursor can verify in the code and what only the shop owner knows.

## Example: a ceramics shop launches three new mugs

Imagine a ceramics shop whose developer-owner adds three mugs to the product data file and merges the change. In Cursor she asks for a Facebook post for each new item. Cursor reads the product file for names, colours and prices, finds the matching photos with `list_media` and notices that one mug has no price in the file. She fills it in. Cursor writes three posts of about 50 words each, uses the live product URLs as links and saves the drafts with `create_drafts` for the shop's Page. She checks stock in the shop admin, which Cursor cannot see, and requests a Thursday 18:00 slot for the first mug.

## Step by step

1. **Point Cursor at the product data.** Name the file or the commit that adds the products. Cursor reads names, prices and descriptions from the repository, which is more reliable than retyping them from memory.
2. **Let it flag gaps in the data.** Ask Cursor to list products with missing prices, photos or URLs before it writes anything. A gap in the data becomes a hole in the post.
3. **Match photos from the library.** Cursor looks for the product photos with `list_media` by name or tag and reports any product with no photo, rather than picking a lookalike.
4. **Write one short post per product.** Ask for about 50 words per product with the price copied from the data and the product link in the text. Facebook shows a preview card for links in Tareno's configuration.
5. **Save as Page drafts.** Cursor confirms the Page with `list_accounts` and saves the posts through `create_drafts`. Facebook publishes as the Page, so make sure it is the shop's.
6. **Confirm stock, then request a time.** Check stock in the shop admin yourself, because Cursor sees the repository and not the warehouse. Then give a day, a time and an IANA time zone; the requests become pending actions you approve in the dashboard.

## Prompts to copy

### Find gaps in the data

```text
Read the new entries added in [commit or file] and list every product with a missing price, photo name or product URL. Do not write any post until I have filled the gaps, and say which fields you would use for the post text.
```

### Match the photos

```text
Use Tareno to look up the product photos for [mug names] in my media library and report which product has no matching photo. Return a table with product, price from the file and photo name.
```

### Write the posts

```text
Write one Facebook Page post of about 50 words for each new product, copying name, colour and price exactly from the product file and adding the product URL. Do not add claims about materials or shipping that are not in the file.
```

### Save the drafts

```text
Use Tareno to confirm the Facebook Page [shop name] and save the three approved posts with their photos as drafts. Return a table with draft ID and product, and request no time until I have checked stock in the admin.
```

## Facebook in Tareno

- Facebook posts in Tareno take up to ten images and a link with a preview card, so a product post can show the mug in two photos and link to the page that sells it.
- Tareno can read comments on Facebook, so Cursor can pull out the questions shoppers ask under a launch, such as dishwasher safety, and suggest a line for the product description.
- Meta's documentation says scheduled API posts need a time between 10 minutes and 30 days ahead, which fits a launch planned over a week.
- Meta's documentation says the Pages API posts as the Page and that an app can edit only the posts it created.

Official rules ([Meta: Pages API, posts](https://developers.facebook.com/docs/pages-api/posts), checked 2026-10-24):

- The Pages API posts as the Page. The person using it must be able to perform the Page tasks CREATE_CONTENT, MANAGE and MODERATE.
- A scheduled post needs a publish time between 10 minutes and 30 days after the API request.
- An app can update a Page post only if that app created it.

## Mistakes to avoid

- Announcing a product that is not in stock. Cursor cannot see inventory, so check the admin before you approve a request.
- Trusting a price from a stale branch. Make sure Cursor reads the merged data, not an older working copy.
- Adding claims to the post. Anything about materials or care that is not in the product file should be checked by the owner.
- Posting the link to a product page that is not published yet. Open the link before you approve the request.

## What does not work

- Cursor cannot see live stock or order data unless you provide it, so the owner confirms availability before approval.
- It cannot edit a post that was created directly on Facebook, since Meta lets an app update only the posts it created.
- It cannot make a post go live on its own, because a time request becomes a post only after you approve it in the Tareno dashboard.

## Frequently asked questions

### Can Cursor write Facebook posts from product data?

Yes. It reads names, colours and prices from the repository, matches photos from your Tareno library and writes a short post for each item. You check stock and wording, and you approve the time in Tareno.

### Does Cursor know what is in stock?

Only if you tell it. It sees the repository, not your warehouse or shop admin, so confirm availability yourself before you approve a request for a product post.

### Which photos does it use?

The ones in your Tareno media library. Cursor looks them up by name or tag and tells you when a product has no photo, so you upload it instead of letting it guess.

### Can it add the product link?

Yes. Links are supported in Facebook text in Tareno's configuration and get a preview card, so Cursor can take the URL from the product file and put it in the post.

### Can Cursor learn from the comments under a launch?

It can read and group them with `list_post_comments`, because Tareno exposes comment reading for Facebook. It cannot reply to shoppers, so you answer them on Facebook yourself after reading the grouped questions.

### Will the launch post go out without my approval?

No. A time request is a pending action in Tareno, and Facebook receives the 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`
- `list_post_comments`
- `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

- [Cursor × Tareno overview](https://tareno.co/agents/cursor)
- [Facebook with Tareno](https://tareno.co/channels/facebook)
- [Media library](https://tareno.co/features/media-library)
- [Approval workflows](https://tareno.co/features/approval-workflows)