> For the complete documentation index, see [llms.txt](https://studio0.gitbook.io/tome-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio0.gitbook.io/tome-docs/tags-and-auto-tagging.md). # Tags & Auto-tagging Tags are little emoji labels you stick on your cards so you can find them again later with `%collection`. Could be a custom server emoji, a regular emoji, or just typing a name with colons like `:vhs:`. ## Tagging by hand | Command | What it does | | ----------------------------- | ------------------------------------------------------------------ | | `%tag [card id(s)]` | Tag a card. Skip the ID and it tags whatever you got most recently | | `%untag [card id(s)]` | Take a tag off. Same deal, skip the ID for your most recent card | A card can have as many tags as you want, `%tag` just adds another one rather than replacing what's there. Tag more than one card at once by listing them, comma or range separated: `%tag :vhs: 275, 274, 265-260` tags all four in one go. Works the same way for `%untag`. ## Auto-tag Set up a rule once and the bot tags things for you automatically from then on, no need to do it by hand every time. | Command | What it does | | ----------------------------- | ---------------------------------------------------------------------------------------- | | `%autotag ` | Make a rule for that emoji and tag everything in your collection that matches right away | | `%autotag list` | See your rules | | `%autotag remove ` | Delete a rule and clean up whatever it tagged | Making a new rule for an emoji that already has one just swaps it out. You can't stack two rules on one emoji. Free accounts get up to 5 auto-tag rules at once - Tome+ raises that considerably, see Currencies & Daily Rewards. Swapping out a rule for an emoji you already have one on never counts against the limit, only a genuinely new one does. ### Writing a rule Mix and match any of these: * `4 star` for a specific star count, 1 through 5 * `A3` for a specific Ascended level, A1 through A5 * `s: ` to match a series * `c: ` to match a character * `misprint` for misprints only * `poster` for posters only * `event` for any holiday art at all A few examples: * `%autotag :vhs: 4 star` tags every 4 star card * `%autotag :heart: c: Aiki Himizu s: Blue Lock` tags only that exact character from that exact series * `%autotag :fire: misprint` tags every misprint you own * `%autotag :sparkle: poster 5 star` tags five star posters * `%autotag :crown: A3` tags every A3 Ascended card you own ### When you've got more than one rule If a card matches a few of your rules at once, whichever one is more specific wins (basically, whichever rule you packed the most conditions into). If it's a tie, whichever one you made most recently wins. Auto-tag only ever touches the one tag it put on a card itself. Anything you tagged by hand with `%tag` is safe, even if a rule uses the exact same emoji. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://studio0.gitbook.io/tome-docs/tags-and-auto-tagging.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.