linkyun-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKYUN_OPS_TOKEN | Yes | Ops token for authentication | |
| LINKYUN_OPS_CLIENT | No | Client identifier (default: linkyun-ops-mcp) | linkyun-ops-mcp |
| LINKYUN_OPS_BASE_URL | Yes | Base URL of the LinkYun Ops API | |
| LINKYUN_OPS_TIMEOUT_MS | No | Timeout in milliseconds (default: 10000) | 10000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ops_list_metricsA | List LinkYun operations metrics available to the configured token. |
| ops_query_metricC | Query one LinkYun operations metric. Send explicit RFC3339 ranges and the backend query contract only. |
| ops_get_home_recommendationsC | Get current home banner, platform recommendation, and hot ranking configuration. |
| ops_preview_home_recommendationsA | Validate and preview a partial home recommendation config without writing changes. Only supplied modules are replaced; omitted modules are preserved. |
| ops_set_home_recommendationsA | Replace supplied home recommendation modules for a workspace. Omitted modules are preserved. Requires a reason. |
| ops_list_agentsC | List or find agents in a workspace for operations management. Supports filters for agent_code, status, hidden, limit, and offset. |
| ops_get_agentA | Get one workspace agent by agent_code, including status, hidden flag, category, and display tags. |
| ops_list_agent_tagsB | List active frontend-visible Agent tag dimensions/tags and discover category mappings. |
| ops_update_agentB | Update one workspace Agent operations fields: status, hidden flag, category_key, and display_tag_keys. Requires a reason. |
| ops_get_tracking_summaryC | Query one LinkYun campaign tracking funnel summary. Convert relative dates to explicit RFC3339 timestamps before calling. |
| ops_get_tracking_breakdownC | Compare campaign tracking funnels grouped by link_id, source, or campaign. Convert relative dates to explicit RFC3339 timestamps before calling. |
| ops_get_tracking_trendC | Query campaign tracking funnel trends by hour or day. Requires explicit RFC3339 created_from and created_to. |
| ops_list_tracking_short_linksC | List campaign short-link configurations. Optionally include per-link funnel metrics for an explicit time window. |
| ops_create_tracking_short_linkC | Create a campaign short-link configuration. Requires a reason for backend audit. |
| ops_update_tracking_short_linkC | Update a campaign short-link configuration by code. Requires a reason for backend audit. |
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 15 tools
Each tool targets a distinct resource and action: agents, short links, home recommendations, tracking, and metrics are all clearly separated. There is no ambiguity between similar tools like list vs get or summary vs breakdown.
All tools follow the consistent pattern 'ops_{verb}_{noun}' (e.g., ops_list_agents, ops_create_tracking_short_link). Verbs like get/list, create/update, and preview/query are used consistently for their respective operations.
With 15 tools, the server covers multiple sub-domains (agents, short links, home recommendations, tracking, metrics) without being bloated. Each tool serves a clear purpose, and the count is well-scoped for the operations management domain.
The tool surface covers core CRUD and query operations for agents, short links, home recommendations, and tracking. Minor gaps exist, such as missing delete operations for short links or agent creation, but these are likely handled by other systems or are out of scope for this ops server.