networklytics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETWORKLYTICS_API_KEY | No | Your API key for NetworkLytics, required for certain tools like get_analysis_by_id | |
| NETWORKLYTICS_API_URL | No | The URL of the NetworkLytics API server | https://networklytics.com |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_shared_analysisA | Retrieve a YouTube comment network analysis result from a public NetworkLytics share link. Returns network statistics (nodes, edges, density, communities), top influencers with centrality scores, sentiment analysis, topic keywords, and AI-generated insights. Use this when a user shares a NetworkLytics share URL or token. |
| get_analysis_by_idB | Retrieve a YouTube comment network analysis by its ID. Requires API key authentication (set NETWORKLYTICS_API_KEY environment variable). Returns the same structured data as get_shared_analysis. |
| get_api_infoB | Get NetworkLytics API information and available endpoints. |
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 3 tools
Each tool has a clearly distinct purpose: get_analysis_by_id retrieves a specific analysis by ID with authentication, get_api_info provides API metadata, and get_shared_analysis fetches public analysis from a share link. There is no overlap or ambiguity in their functions.
All tools follow a consistent verb_noun pattern with snake_case (get_analysis_by_id, get_api_info, get_shared_analysis). The naming is predictable and uniform throughout the set.
With only 3 tools, the set feels thin for a network analytics server. It lacks essential operations like creating, updating, or deleting analyses, which limits functionality and makes the server seem incomplete for its domain.
The server is severely incomplete for network analytics. It only provides retrieval and info tools, missing core operations such as initiating analyses, managing data, or performing CRUD actions. This will cause significant agent failures in handling typical workflows.