Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

List weekly drops

list_weekly_drops
Read-onlyIdempotent

Lists a brand's recent Weekly Drops, the weekly batches of ad ideas that Autopilot prepares: up to 12, each with its period, status, result count and timestamps. Read-only; starts no batch. get_automation_status shows the settings behind them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand_id": "<brand_id>"
    },
    "name": "list_weekly_drops"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_idYesBrand id from list_brands.
max_resultsNoWeekly Drops to return, 1 to 12 (default 12).
response_formatNoOutput format: text (default) or json. table is not available for this tool.

Output Schema

NameRequiredDescriptionDefault
dropsNoRecent Weekly Drops for the selected brand.
feature_enabledNoWhether this automation feature is enabled in this environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / brand_id / description
      Previous value: -"Brand reference from list_brands (e.g. the returned brand id)."New value: +"Brand id from list_brands."
    • changedInput schema / properties / max_results / description
      Previous value: -"Maximum number of results in this bounded response; constrained by the field maximum."New value: +"Weekly Drops to return, 1 to 12 (default 12)."
    • changedInput schema / properties / response_format / description
      Previous value: -"Output format: text or json for capped research examples; table is available only for tracked rival rows."New value: +"Output format: text (default) or json. table is not available for this tool."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only; starts no batch' largely restates the structured safety profile. The genuinely additive content is behavioral scope — up to 12 items, each containing period, status, result count and timestamps, prepared by Autopilot — which tells the agent what state the data reflects rather than how to call it.

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?

Two sentences, front-loaded with the verb and resource, with the sibling reference placed last where an agent needs it after understanding the tool. Minor waste in 'Read-only; starts no batch,' which duplicates the annotations, but the parenthetical definition of Weekly Drops earns its length.

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

Completeness4/5

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

With an output schema present, the description need not detail return fields, and readOnly/destructive behavior is covered by annotations, so the remaining burden is small. It covers purpose, safety and the settings sibling; only edge cases like empty results or ordering are unaddressed, which is acceptable for a simple list operation.

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%, including the 1–12 bounds on max_results and the 'Brand id from list_brands' hint, so the description has little room to add meaning. 'Up to 12, each with its period, status...' mirrors the schema's default and maximum rather than explaining any parameter behavior beyond it. Baseline 3 applies.

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?

Specific verb plus resource ('Lists a brand's recent Weekly Drops') and it explicitly defines the domain term as 'the weekly batches of ad ideas that Autopilot prepares,' so an agent unfamiliar with the concept still understands what comes back. It also contrasts itself with get_automation_status, making it distinguishable from the nearest sibling.

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?

It states the read-only nature and clarifies 'starts no batch,' which is the key misuse risk for a tool whose name implies triggering drops, and it routes the agent to get_automation_status for settings. There is no explicit when-not-to-use or note about what to do if zero drops exist, so it stops short of full routing guidance.

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

All StealAds toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources