Gloriads — Amazon Ads

A rule's last runs

list_rule_runs

Read-onlyIdempotent

List one rule's last 20 runs, newest first: how many objects each examined, matched and changed, and its operation ids (see list_activity). Tests are not listed.

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": {
      "rule_id": "<rule_id>"
    },
    "name": "list_rule_runs"
  }
}

Input Schema

Name	Required	Description	Default
`rule_id`	Yes	The rule: an `id` from list_rules.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: the hard cap of 20 runs, the newest-first ordering, the exclusion of tests, and the shape of the returned metrics. It stops short of describing any pagination or windowing behavior beyond the cap.

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?

One front-loaded sentence with the cap and ordering stated first, then the payload contents, then the sibling pointer and the exclusion. No filler or redundancy.

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?

With no output schema, the description carries the burden of telling the agent what comes back and it does so: per-run examined/matched/changed counts plus operation ids, bounded at 20 and ordered newest-first. For a one-parameter read tool, nothing needed for correct invocation is missing.

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% and the single parameter is already documented as 'an id from list_rules'. The description reinforces the single-rule scope ('one rule's last runs') but adds no syntax or format detail beyond the schema, so 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 ('List') plus resource ('one rule's last 20 runs') plus exact scope and return contents (examined/matched/changed counts, operation ids). It differentiates itself from list_rules (which enumerates rules) and points at list_activity for the underlying operations, and it explicitly excludes tests.

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?

The usage context is clear: inspect the recent history of a single existing rule, with a pointer to list_activity for the operation detail behind the ids. The scope exclusion ('Tests are not listed') prevents a wrong call, though no explicit when-not/when-to-use-other-runs-source statement is given.

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

All Gloriads — Amazon Ads tools Inspect

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

Need Help?