Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

Get automation status

get_automation_status
Read-onlyIdempotent

Returns the Autopilot settings of one brand: whether weekly ad preparation is on, its cadence and day, how many ads each batch may make, and whether the brand has enough source ads for it. Read-only: turns nothing on, changes no setting and starts no batch. feature_enabled false means Autopilot is not switched on in this environment.

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

Input Schema

NameRequiredDescriptionDefault
brand_idYesBrand id from list_brands.
response_formatNoOutput format: text (default) or json. table is not available for this tool.

Output Schema

NameRequiredDescriptionDefault
automationNoAutomation settings and source readiness for the selected brand.
feature_enabledNoWhether this automation feature is enabled in this environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / 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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and no destructive behavior, but the description reinforces this with concrete language: it turns nothing on, changes no setting, and starts no batch. It also explains the meaning of feature_enabled=false, which is useful behavioral context beyond the 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 two tight sentences and front-loads the return content before the read-only caveat. Every clause adds useful information: the settings returned, the safety profile, and the feature-flag interpretation.

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 read-only status tool with an output schema, rich annotations, and fully documented parameters, the description supplies enough context to call it correctly. It covers what is returned, that it is non-mutating, and how to interpret the key feature_enabled field.

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 brand_id and response_format are already documented in the schema. The description adds no extra syntax or format detail for either parameter; it only implies that the tool operates on a single brand.

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 uses a specific verb and resource: returns Autopilot settings for one brand. It enumerates the concrete settings included, such as weekly ad preparation, cadence, batch size, and source-ad sufficiency, which makes the tool's scope unambiguous.

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

Usage Guidelines3/5

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

The read-only framing and brand-level scope imply when the tool is appropriate, but there is no explicit guidance on when to use it versus siblings such as get_ad_status or get_tracking_status. It also lacks stated exclusions or prerequisites beyond the schema-provided brand_id reference.

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