TextRazor
for LuumenAI
Read meaning out of incident text, and manage the dictionaries behind it
TextRazor turns free text into structured signal. Point Luumen at a stream of tickets, postmortems, or alert descriptions and it extracts entities, classifies topics, and runs a full analysis pass in one step. When the extraction misses your internal service names, Luumen can update the custom dictionaries and classifiers behind it as an approved change.
The TextRazor toolbox
6 tools: 4 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Account InformationThis tool retrieves comprehensive information about a TextRazor account, providing essential details about the account's status, usage, and limits.
- ReadClassify TextClassify text into predefined categories using TextRazor's classification capabilities.
- ReadExtract Named Entities from TextExtract named entities (people, places, companies, etc.) from text using TextRazor's entity extraction API.
- ReadAnalyze Content with TextRazorA comprehensive content analysis tool that combines multiple TextRazor extractors to perform a complete analysis of the input text.
- WriteManage Custom ClassifiersThis tool manages custom classifiers in TextRazor, allowing users to create, update, and manage custom classification categories. Approval by default
- WriteDictionary ManagerManage custom entity dictionaries in TextRazor for enhanced named entity recognition. Approval by default
One prompt, start to finish
What a governed TextRazor run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — manage custom classifiers, dictionary manager — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to TextRazor — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut TextRazor to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.