Skip to main content
Glama

discovery

by dev.nexbid

create_media_buy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNoAdvertiser brand name (for rules check)
agent_idNoOptional agent identifier (telemetry; feeds ADR-066 behavioral-risk shadow logging).
categoryNoProduct category (for rules check)
end_dateNoCampaign end date (ISO 8601)
bid_centsYesBid amount in cents
start_dateNoCampaign start date (ISO 8601)
campaign_idNoParent campaign UUID. When set, the campaign's default pacing + frequency cap cascade into this buy unless explicitly overridden.
budget_centsYesTotal budget in cents
creative_refNoCreative asset URL or reference
inventory_idYesTarget inventory slot UUID
advertiser_idYesAdvertiser account UUID
agent_mandateNoOptional signed agent mandate (ADR-066). Verified by the auction-entry gate.
creative_dataNoCreative metadata (JSON)
pricing_modelYesPricing model for the buy
quality_scoreNoQuality score 0-1 (default: 0.5)
pacing_strategyNoOverride pacing strategy. Falls back to campaign default, then "even".
context_relevanceNoContext relevance 0-1 (default: 0)
frequency_cap_sessionNoPer-session impression cap for this buy. NULL means defer to inventory cap. Falls back to campaign default, then 3.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=false), the description reveals that this tool 'creates a binding commitment' and must be confirmed with the user. It also explains the validation/auction scoring behavior and return status (approved/rejected). The score formula and rejection-reason hint add further behavioral context.

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?

The description is well-structured into useful sections (tool_description, when_to_use, combination_hints, output_format) and is appropriately sized for an 18-parameter tool. The score formula and combination hints are relevant, though there is minor redundancy between tool_description and output_format regarding return status.

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

Completeness5/5

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

For a complex creation tool with no output schema, the description is highly complete. It covers purpose, prerequisites, output fields, workflow sequencing with siblings, failure handling (rejection_reason), and the scoring formula. It enables an agent to understand the tool's role fully.

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%, so the baseline is 3. The description adds minor semantic value by referencing 'bid', 'quality', and 'context' in the score formula, but does not provide additional explanation for individual parameters beyond what the schema already offers.

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

Purpose5/5

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

The description clearly states the verb 'Create' and the resource 'media buy (bid on publisher inventory)', and explains what it does: 'Validates rules, runs auction scoring, and returns approval/rejection status.' It distinguishes from sibling tools like list_media_buys and submit_creatives.

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

Usage Guidelines4/5

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

The 'when_to_use' section explicitly says when to call ('When an advertiser wants to place a bid') and provides a prerequisite ('Requires inventory_id from list_inventory/get_inventory_item'). It also warns to always confirm with the user because it creates a binding commitment. However, it does not explicitly state when not to use or name alternatives, though the combination hints imply workflow order.

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

All discovery toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between get_product and nexbid_product, which are explicitly described as aliases, and between list_products and nexbid_search with content_type='product'. This could cause confusion, though descriptions help clarify. Other tools like activate, pause, and cancel are well-differentiated for media buy lifecycle management.

Naming Consistency3/5

The naming is mixed with no consistent pattern. Some tools use verb_noun (e.g., create_media_buy, list_inventory), others use noun_verb (e.g., nexbid_search, nexbid_purchase), and some are single verbs (e.g., activate, pause, cancel). While readable, the lack of a uniform convention across the set reduces predictability.

Tool Count4/5

With 19 tools, the count is on the higher side but reasonable for the dual domains of media buying and marketplace discovery. It covers operations like listing, creating, managing, and reporting, which justifies the number. However, it borders on feeling heavy, especially with overlapping tools like get_product and nexbid_product.

Completeness5/5

The tool set provides comprehensive coverage for both media buying (create, submit, activate, pause, cancel, track, settle, report, compliance) and marketplace discovery (search, categories, product details, purchase, order status). There are no obvious gaps; workflows are well-supported with clear combination hints, ensuring agents can handle end-to-end tasks without dead ends.

Resources