> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alura.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Your shop

> MCP tools to read what Alura changed on the listings of your own connected Etsy shops

These tools read your own connected Etsy shops as Alura stores them. They never change anything on Etsy. They need the `workspace:read` scope.

## Try these prompts

| Ask your assistant | Tools it uses |
| - | - |
| What did Alura change on my listings last week? | `list_my_changes` |
| Which of my listings did an AI optimization change, and what did it change? | `list_my_changes` |

## Good to know

* **Changes made in Alura.** The change log holds the writes made through Alura. Edits made directly on Etsy, or with other tools, aren't in it. Changes made in the Alura app are history only and can't be reverted.
* **Some Alura writes go around it.** Alura's A/B tests (their listing, inventory, photo and video changes) and the legacy app at app.alura.io (its edits, photos, videos, auto-renew and publishing) write to Etsy without the change log, so their changes can be missing.
* **Every connected shop by default.** Lists cover all of the workspace's connected shops unless you name one. Each change says which shop its listing belongs to.
* **Listing text stays data.** Before and after values hold your listings' own text, and the assistant gets them as data only.

## Tools

### `list_my_changes`

**List my changes.** List the changes Alura made to the user's own Etsy listings (their connected shops in Alura), newest first: which fields changed, from what to what, when, who made it and where it came from (app, automation, ai\_optimize, ai\_create, revert). Use it to answer "what did Alura change on my listings last week?". Filter by shop\_id, listing\_id, source and a from/to time range; give `id` (chn\_...) for one change. Changes made directly on Etsy are not in it, and changes from Alura's A/B tests or the legacy app.alura.io can be missing; changes made in the Alura app are history only (not revertable). Pass next\_cursor back as cursor for the next page; detail: "concise" lists the changed field names without their values. A change too large to show here whole is trimmed: its largest before and after values (such as an inventory) read null and are named in the field's `omitted`; the full change is on REST GET /v1/workspace/changes/{id}.

* **Cost of `list_my_changes`:** 1 API credit per page, or 1 API credit per call.
* **Behavior:** Read-only: changes nothing. Works on Alura's own data only.
* **Scope:** `workspace:read` (read your shops' listings, stats, reviews and settings).
* **REST:** [`GET /v1/workspace/changes`](/api-reference/workspace/changes/list), [`GET /v1/workspace/changes/{id}`](/api-reference/workspace/changes/get).

| Argument | Type | Required | Description |
| - | - | - | - |
| `id` | string | No | One change by its ID (chn\_...), with every field it changed; leave out to list changes. |
| `shop_id` | string\[] | No | Only these connected shops, by their Etsy shop IDs; default every connected shop. |
| `listing_id` | string | No | Only changes to this listing, by its Etsy listing ID. |
| `source` | `app`, `api`, `automation`, `ai_optimize`, `ai_create`, `revert` | No | Only changes from this source. |
| `from` | string | No | Made at or after this time: YYYY-MM-DD or an ISO 8601 date-time. |
| `to` | string | No | Made before this time: YYYY-MM-DD or an ISO 8601 date-time. |
| `cursor` | string | No | next\_cursor from the previous page of the same list. |
| `limit` | integer | No | Changes per page, 1-20 (default 20). |
| `detail` | `concise`, `detailed` | No | `detailed` (default): every field this tool shows. `concise`: the key fields only, for long lists or a quick check. |

**Example arguments**

```json theme={null}
{
  "source": "ai_optimize"
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.