Citlyze
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CITLYZE_API_KEY | No | API key for the Citlyze workspace, used as a bearer token for authentication. Optional: without it the server starts in discovery mode (initialize and tools/list only). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_workspace_overviewA | Workspace name, target brand, active prompt/location/engine counts, competitors, and the latest completed measurement window. |
| list_promptsA | List tracked prompts with text, intent, tier, and active state. |
| list_measurement_windowsA | List measurement windows (tracking snapshots), newest first. |
| get_visibility_overviewB | Headline AI visibility metrics per brand and engine for a measurement window. |
| get_prompt_visibilityB | Per-engine and per-location visibility metrics for a single tracked prompt. |
| list_citationsB | Domains cited in AI answers, grouped with citation counts and sample URLs. |
| list_recommendationsC | AI visibility optimization recommendations, highest priority first. |
| list_competitor_visibilityB | Compare AI visibility across the target brand and tracked competitors. |
| list_crawler_eventsC | Daily AI crawler visits (GPTBot, ClaudeBot, PerplexityBot, Bingbot, and more) on tracked sites. |
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 9 tools
Each tool addresses a distinct data object or report: workspace, prompts, windows, visibility, citations, recommendations, competitors, and crawler events. The only close pair is get_visibility_overview vs get_prompt_visibility, but one is brand/engine-level and the other is prompt-specific, so they are clearly separable.
The set consistently uses snake_case with get_ for singular/detail reports and list_ for collection-style reports. Even list_competitor_visibility returns a comparison list, aligning with the list_ pattern.
Nine tools fit a focused analytics server well, covering the major query surfaces without redundancy or bloat.
For a read-only AI visibility analytics domain, the coverage is comprehensive: workspace context, prompt tracking, measurement windows, visibility, citations, recommendations, competitor comparisons, and crawler events all have dedicated tools. No obvious gaps or dead ends in the workflow.