GAM Seller MCP Node
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| well_known_capabilitiesB | Return the signed RS256 capability document for this Seller MCP Node. |
| discover_productsB | Discover coarse product families available to this buyer. |
| get_forecastA | Get a coarse availability forecast (Low/Mid/High) for a product family and period. |
| check_availabilityA | Check whether the publisher can deliver a number of impressions of a product family in a period. Returns available, partial (with the volume it can offer) or unavailable, the viewable share when forecast, and — if the volume does not fit — up to 3 alternative periods or families where it does. Figures are forecast estimates, rounded down (2 significant figures by default), not reservations. |
| create_intentA | Register a firm buying intent over a product family at its current firm price (soft commitment with TTL). Not a GAM order or inventory hold. |
| revoke_intentA | Revoke one of your own active intents by id. Idempotent per client_request_id. |
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 6 tools
Most tools target distinct operations: capability discovery, product discovery, coarse forecasting, specific availability check, and intent create/revoke. The main overlap is between get_forecast and check_availability, which both deal with availability but differ in granularity (coarse Low/Mid/High vs. specific volume with alternatives); descriptions help distinguish them.
Five of six tools follow a clear verb_noun or verb_noun_phrase pattern (discover_products, get_forecast, check_availability, create_intent, revoke_intent). well_known_capabilities breaks the pattern as a noun phrase rather than a verb-led action, but the convention is otherwise consistent.
Six tools is well-scoped for a seller-side MCP node covering authentication metadata, product discovery, forecasting, availability checking, and intent lifecycle. Each tool earns its place without obvious redundancy or bloat.
The surface covers discovery, forecast, availability, and intent create/revoke, but lacks read operations for intents (e.g., list_intents or get_intent) and any explicit price lookup despite create_intent relying on current firm price. An agent can work around this only if create responses include sufficient identifiers, making it a notable gap.