Skip to main content
Glama
juan-sibbo

GAM Seller MCP Node

by juan-sibbo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

discover_products

Retrieve coarse ad product families available to the authenticated buyer, enabling read-only inventory discovery in Google Ad Manager.

Instructions

Discover coarse product families available to this buyer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNoBuyer bearer JWT (RS256, aud=seller-mcp-node). Identity is derived from token.sub.
client_request_idNoClient-supplied idempotency key for replay detection

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
-]
  2. Changed1 schema field changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations, and description fails to disclose behavioral traits such as read-only nature, authentication via token, or idempotency behavior. Only parameter descriptions hint at JWT usage.

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?

Single sentence, no fluff. Appropriate length for a simple discovery tool, but could include more useful details.

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

Completeness2/5

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

Given 2 params and no output schema, description lacks context about return format, authentication requirements, or how buyer identity is resolved. Not complete for an agent to use confidently.

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 coverage is 100%, so baseline 3. Tool description adds no extra meaning beyond what parameter descriptions provide.

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 the tool discovers coarse product families for a buyer. Clear verb-resource but 'coarse' is vague. No differentiation from siblings.

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?

No guidance on when to use or when not to use. No mention of alternatives or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/juan-sibbo/gam-seller-mcp-node'

If you have feedback or need assistance with the MCP directory API, please join our Discord server