Billboardbug MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BILLBOARDBUG_API_KEY | Yes | Your Billboardbug API key from app.billboardbug.com → Settings → API Keys. Sent via the X-Api-Key header. |
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 |
|---|---|
| create_dealA | Create a live billboard deal at a real location. Requires an uploaded image or video. Returns storefrontId and billboardId. Never sets featured (paid) placement. |
| update_dealB | Replace an existing deal (same fields as create_deal). Use isEnabled:false to take a deal down when the promotion ends. |
| get_dealA | Read a deal back by storefrontId and billboardId to verify it is live. Works without an API key. |
| list_my_dealsB | List deals owned by the API key's account. |
| list_categoriesA | List storefront categories for categoryId (about 7,000). Pass nameContains to filter. Requires an API key. Default used by create_deal is Miscellaneous. |
| search_dealsB | Search BillboardBug deals by text (min 3 characters). Requires an API key. |
| upload_mediaA | Upload a local image/video file (or base64 data) to BillboardBug. Use billboard-image/billboard-video for deals, post-image/post-video for chirps. Returns the blob id. |
| generate_imageA | Generate billboard artwork from a prompt (recommended 640x373). Returns base64 data URIs you can pass to upload_media. Prefer realistic photos. |
| create_chirpC | Post a chirp (social post) on BillboardBug, e.g. announcing a new billboard. Returns the chirp id. |
| update_chirpC | Edit an existing chirp you own. |
| get_chirpA | Read a chirp back by id to verify it posted. |
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 11 tools
Tools split cleanly into deals (get/create/update/list/search), chirps (create/update/get), and media (upload/generate), each with a distinct verb+resource target. Minor potential confusion between the read-oriented deal tools (get_deal, list_my_deals, search_deals), but descriptions clarify their different retrieval modes.
Every tool follows a consistent snake_case verb_noun pattern (get_deal, create_chirp, update_deal, list_my_deals, upload_media, generate_image). Verb choices are predictable across the resource set.
Eleven tools is well-scoped for a two-domain server (deals + chirps) with supporting media utilities. Each tool maps to a clear operation with no redundant filler.
Deals get near-full lifecycle coverage (create/read/update/list/search, with takedown via isEnabled:false), and media/chirp creation are supported. Gaps remain: no delete_chirp, no list_chirps, and no deal delete outside the isEnabled flag, but these are minor workarounds.