Skip to main content
Glama
GAM Seller MCP Node

GAM Seller MCP Node

discover_products

Read-only

Identify coarse product families available to a buyer in Google Ad Manager, enabling read-only ad inventory discovery before forecasting.

Instructions

Discover coarse product families available to this buyer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoBuyer bearer JWT (RS256, aud=seller-mcp-node). Identity is derived from token.sub.
client_request_idNoIdempotency key for replay detection — required on every call unless the operator opted out; fresh value per call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.1
    • changedInput schema / properties / client_request_id / description
      Previous value: -"Client-supplied idempotency key for replay detection"New value: +"Idempotency key for replay detection — required on every call unless the operator opted out; fresh value per call"
  2. Changed3 schema fields changedv0.8.0
    • removedInput schema / properties / buyer_id
      Removed value: -{
      -  "description": "Buyer identifier (opaque, B2B)",
      -  "type": "string"
      -}
    • changedInput schema / properties / token / description
      Previous value: -"Domain-2 inter-service JWT (RS256)"New value: +"Buyer bearer JWT (RS256, aud=seller-mcp-node). Identity is derived from token.sub."
    • removedInput schema / required
      Removed value: -[
      -  "buyer_id"
      -]
  3. Changed1 schema field changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful qualifier 'coarse', implying the result is an aggregated/high-level view rather than a full catalog, but it says nothing about pagination, filtering, or that identity comes from the token.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient, though 'coarse' carries a lot of unexplained weight for one adjective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only discovery tool with annotations covering safety and a 100%-covered schema, the remaining gap is the return shape: there is no output schema, yet the description does not characterize what a 'coarse product family' looks like or how results are ordered/limited. Adequate but leaves an agent guessing about output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and both parameters (token, client_request_id) are documented in the schema itself with detail on RS256/JWT and idempotency. The description adds nothing beyond that, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('discover') and resource ('product families') with a scope qualifier ('available to this buyer'). It is distinguishable from siblings like get_forecast or check_availability, though it does not name what makes it different beyond the resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as well_known_capabilities, which a sibling for discovery/capability listing. The agent must infer the entry point from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.