Ten Things to Ask an Assistant Connected to X02

Worked examples rather than a tool reference — finding a file by the name it had on your machine, tidying a month of uploads into folders, publishing an album, and batch jobs that need a quota check first.

By X02 Team · 2026-09-22 · MCP, AI, Workflows, Tutorial, Productivity

Once X02 is connected, the tools disappear. You do not call move_files — you say "put this week's screenshots in a folder" and something sensible happens. The gap between those two sentences is where people get stuck: knowing the tools exist does not tell you what is worth asking for.

These are ten requests that work well, and the reason each one does.

[!TIP] Quick Navigation:

• Finding things
• Tidying up
• Sharing
• Batch jobs
• Where it struggles
• Next Steps & Related Tutorials

Finding things

1. "Find the invoice PDF I uploaded last month"

Why it works: search matches the original name, not just the generated one.

This is the single most useful thing the connection does, and it is not obvious. X02 renames files on upload — invoice-march.pdf becomes something like aB3xY9.pdf — but it keeps your original name alongside it, and search covers both. So you can ask for a file by the name it had on your machine, months later, without ever having seen the short one.

Search is fuzzy, which cuts both ways. Results come back labelled [exact match] or [fuzzy match], and a fuzzy match may not contain your search term at all. A well-behaved assistant will tell you which it found rather than presenting a near-miss as certain. If it hands you one confident answer to a vague query, ask it to list what it found.

2. "What is aB3xY9.png?"

Why it works: view_file returns the picture, not the metadata.

A generated filename tells you nothing, and it tells the assistant nothing either. view_file hands it a downscaled thumbnail so it can actually look — useful before acting on something, and the difference between "I found a file called aB3xY9.png" and "that is the pricing table screenshot."

It returns a thumbnail, not the original, so it is enough to recognise a screenshot but not to read fine print off one. Images only: PDFs, videos and archives have no preview.

3. "What are my ten largest files?"

Why it works: list_files sorts by size, views, name or date, and narrows by file kind and upload date before it sorts.

Straightforward, and the quickest way to work out where your storage went. "What are my most-viewed files?" works the same way, which is a better question than it looks if you are trying to decide what to keep.

Tidying up

4. "Make a folder called Release v3 and move everything from this week into it"

Why it works: two tools, one sentence.

create_folder then move_files. The move takes a list, so it is one call rather than thirty, and it partially succeeds by design — if three files out of thirty fail, you get twenty-seven moved and three named, not a silent rollback. Ask what failed if the count does not match.

5. "Rename these to something I can actually read"

Why it works: renaming does not break the link.

Worth being precise about what happens here, because it is the most common misunderstanding about X02. Renaming changes the stored filename, and the public URL contains the stored filename — so the URL changes with it. If you have already pasted a link somewhere, renaming breaks it.

If what you actually want is to swap the file behind a link that is already in circulation, that is a different operation: see replacing a file without changing its link.

6. "Move everything out of the Screenshots folder and delete it"

Why it works: deleting a folder does not delete its files.

Files in a deleted folder return to your root library. So the "move everything out" half is unnecessary — deleting the folder does it for you. Worth knowing before you ask an assistant to do the long version.

Deleting a file is another matter entirely. There is no trash can, the URL stops working immediately, and it cannot be undone. Both delete tools are marked destructive so your client can prompt you first; if yours does, read the prompt.

Sharing

7. "Share the Screenshots folder and send me the album link"

Why it works: share_folder publishes and returns the link in one step.

The folder becomes a public album that anyone holding the link can open. There is no sign-in and no access list — the link is the permission, so treat it like a password.

Two follow-ups worth knowing exist: "stop sharing that folder" unpublishes it, and "give that album a new link" regenerates it, which invalidates the old one. The second is what you want when a link has spread further than you intended.

8. "Upload this and make it expire in a week"

Why it works: both upload tools take an expiry.

1h, 6h, 1d, 7d or 30d. After that the file deletes itself. Good for anything you are sending to one person for one purpose — a screenshot in a support thread, a build someone needs today. Omit it and the file is permanent.

Batch jobs

9. "How much of today's upload quota do I have left?"

Why it works: get_account reads live usage, not a cached number.

Ask this before a batch, not after it fails halfway. It returns your plan, uploads used and remaining today, storage used against your limit, and the largest single file your plan allows.

MCP is not a separate allowance — the same daily limit applies whether you upload through an assistant, the website or ShareX: 250 a day on a registered account, 1,500 on Pro.

10. "Rehost all of these image URLs on my account"

Why it works: the bytes never pass through the conversation.

Give it a list of URLs and it works through them. This is the one genuinely high-volume thing the connection does well, because upload_from_url fetches server-side — nothing is base64-encoded into the chat, so there is no context cost per file and no size ceiling beyond your plan.

Images only, though. A list of PDF links will fail on every row.

Where it struggles

Attachments in the chat. An assistant can look at a file you attached but cannot hand the bytes to X02 — no client exposes attachments as URLs. Ask anyway and it gives you a drop link, or pick them up from your tray at x02.me/drop if you dropped them beforehand. Full detail in how to send files to X02 from a chat.

"Delete everything from before June." There is no bulk delete and no date filter on deletion — it would have to list, then delete one file at a time, and there is no undo if it misreads your intent. If you genuinely want that, do it in the dashboard where you can see what you are selecting.

Anything about a file's contents beyond an image. It can see a thumbnail. It cannot read your PDF, transcribe your video or search inside a document. get_file gives it the URL, size, type, folder, view count and expiry — everything except what is inside.

Remembering the connection. A new conversation starts with no memory of the last one. "The file from yesterday" means nothing; "the invoice PDF" means something, because it can search for that.

Next Steps & Related Tutorials

Read this article on X02