adpanel-core
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADPANEL_API_KEY | No | Your AdPanel API key. If unset, tools run in mock mode. |
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 |
|---|---|
| adpanel_ingest_brand_matrixC | Ingest a brand matrix envelope and register source assets with the AdPanel routing gateway. |
| adpanel_orchestrate_cinematic_timelineC | Orchestrate a cinematic timeline from a brand matrix routing reference. |
| adpanel_synthesize_broadcast_assetB | Synthesize a broadcast-ready asset from an orchestrated timeline routing reference. |
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 maps to a distinct stage in a linear pipeline: ingest a brand matrix, orchestrate a timeline, and synthesize a broadcast asset. The descriptions explicitly reference the prerequisite artifact for each later stage, so there is little risk of misselection.
All tools use the same adpanel_ prefix followed by a clear verb_noun pattern in snake_case. The convention is predictable and consistent across the entire surface.
Three tools correspond cleanly to the three core pipeline operations, with each tool earning its place. The count is well-scoped for a focused processing service rather than being artificially thin.
The forward processing chain is covered, but there are no read/list/status operations for brand matrices, timelines, assets, or routing references. Agents can execute the pipeline but may struggle to inspect, verify, retry, or manage previously created artifacts.