activate
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| media_buy_id | Yes | Media buy UUID to activate |
discovery
by dev.nexbid
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
While annotations already indicate a non-read-only operation (readOnlyHint=false), the description adds meaningful behavioral context: activation 'start[s] serving' and requires a creative to be submitted first. The output_format also specifies the return value ('Activated media buy with won_at timestamp'), providing transparency beyond the annotations. It does not contradict any annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is efficiently structured into short labeled sections (tool_description, when_to_use, combination_hints, output_format), with no wasted words. Every section adds distinct value and is easy to scan.
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 simple mutation tool with one parameter and no output schema, the description is complete: it explains what the tool does, when to use it, what must happen before, what happens after, and what the response will be. The combination_hints also integrate it into the broader workflow, covering the tool's context comprehensively.
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?
The single parameter media_buy_id is fully documented in the input schema (100% coverage), including its type and description. The tool description does not add further parameter-specific details beyond what the schema already provides, so baseline 3 is appropriate.
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 states a specific action: 'Activate an approved media buy to start serving.' It clearly identifies the verb (activate), resource (media buy), and the intended effect, effectively distinguishing it from sibling tools like pause, cancel, 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 Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'when_to_use' section explicitly states 'After submit_creatives, when ready to go live with the campaign,' and the description notes the prerequisite 'Requires creative to be submitted first.' The combination_hints further clarify the sequence and mention alternatives (pause, cancel), making usage guidance explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
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.