get_brand_snapshotBundle: all current signals for one brand-day - promotions, price stats + samples, AI-readiness - in one call. 15 credits; no data = no charge.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | eCommerce domain |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description adds cost and billing behavior ('no data = no charge'). Does not describe error handling or response format, but covers key behavioral aspect.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with 'Bundle', no wasted words. Efficient and clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, description lists included signals but not response structure. Adequate for a bundled call given sibling tools exist.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Single parameter with 100% schema coverage; description adds no extra semantics beyond 'for one brand-day' context. Baseline score appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it's a bundle of all current signals for one brand-day, listing specific components (promotions, price stats, AI-readiness). Distinct from sibling tools that provide individual signals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Mentions cost (15 credits) and no-charge policy, implying use when all signals are needed. No explicit exclusions or alternatives, but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of competitive intelligence: coverage, snapshot, price, history, promotions, readiness, and monitoring request. There is no overlap or ambiguity.
Most tools follow a 'get_' prefix pattern, but 'request_monitoring' uses 'request_'. This slight inconsistency is justified by the different action type (request vs. retrieve), but still deviates from the predominant convention.
With 7 tools, the set is well-scoped for a competitive intelligence server. Each tool serves a distinct need without being overwhelming or too few.
The tools cover the main competitive signals: snapshot, price, history, promotions, readiness, and domain monitoring. Minor gaps like listing all monitored domains are absent, but the core workflows are complete.