Perspective API Alternative (Toxicity Detection)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token, used to authenticate the toxicity API calls on Apify. Required for tools/call (the server answers initialize, ping and tools/list without it). Get a token from the Apify Console under Settings > API & Integrations. | |
| PERSPECTIVE_ALT_URL | No | A different URL for the toxicity API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_toxicityA | Score English text for toxicity, severe toxicity, insults, profanity, threats and identity attacks (0-1 probabilities, same attributes as Google Perspective API). Use it to moderate user-generated content, filter LLM output, or triage comments before an agent posts them. Pass up to 100 texts at once. Read-only: it does not store or publish text. Each call is billed to your Apify account ($0.50 for 1,000 text units). The first call after an idle period can take 10 to 30 seconds. English only: non-English text gets a warning field. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of misselection or overlap with a sibling tool. The single tool's purpose (toxicity scoring) is unambiguous and clearly stated.
The lone name 'analyze_toxicity' follows a clean verb_noun snake_case convention. With a single tool there is no opportunity for inconsistent conventions.
A single tool is defensible for a narrow API wrapper, and batching up to 100 texts per call covers the main use case. However, one tool is the thinnest possible surface, leaving no separate operations for things like model/attribute discovery or quota checks.
The scoring operation itself is complete: multi-attribute probabilities, batching, and clear read-only semantics cover the moderation workflow. Minor gaps exist around attribute/language enumeration and rate-limit or quota visibility, but agents can work around these.