Skip to main content
Glama

ads_stockout_check

Read-only

READ-ONLY. Cross-references catalog days of cover (30d cached velocity) with active SP product ads: finds where you are paying for clicks on products close to stock-out. Use for "am I wasting ads budget?", "are ads pushing products that are running out?".

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": "ads_stockout_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
profile_idNoAmazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost.
days_thresholdNoDays-of-cover threshold (default 14)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the leading 'READ-ONLY' merely repeats them. The description does add real behavioral context that annotations cannot: the demand estimate is based on a 30-day cached velocity figure, which tells the agent results are approximate and lagged. It does not describe result volume, pagination, or how items near the threshold are ordered.

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?

Team-oriented and front-loaded: the read-only signal comes first, then the computation, then the natural-language triggers. The 'READ-ONLY' prefix is slightly wasted given the annotation, but no sentence is otherwise padding.

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?

All three parameters are optional and fully described in the schema, and the tool's purpose is unambiguous. However there is no output schema, and the description only sketches the return conceptually ('finds where you are paying for clicks') without indicating what the agent will get back per flagged product or how to interpret a stock-out finding.

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 account_id, profile_id, and days_threshold are each fully documented in the schema, including the default of 14 days. The description adds no additional meaning about threshold sensitivity or which account/profile scope is typical, so it sits at the baseline for a fully documented schema.

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?

States a specific verb and resources: cross-references catalog days of cover with active SP product ads to find click spend on near-stock-out products. This is clearly distinguishable from siblings like ads_list_sp_product_ads (raw listing) or ads_catalog_coverage (coverage gap analysis).

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?

Gives concrete usage triggers in the form of user questions ('am I wasting ads budget?', 'are ads pushing products that are running out?'), which map cleanly to an agent's decision to call it. It stops short of naming exclusions or pointing to a specific alternative tool when the question is about coverage rather than stock-out.

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.

Resources