TrueClicks

Audit rule output table

audit_rule_output_table

Read-only

Get the detailed output rows for the latest completed audit run of one or more rules for one account, as multi-block JSONL: one ">>>>> RuleKey: ..." block per rule, each followed by a JSON Schema line (with the tooltips and column data types) and one JSON object per main row, its detail rows nested under "children". Provides the raw findings behind a failing audit rule. Rules with no completed run in the last 30 days contribute no block.

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": {
      "accountId": "<accountId>",
      "ruleKeys": "<ruleKeys>"
    },
    "name": "audit_rule_output_table"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional maximum rows per rule (defaults to 10000 when omitted).
`ruleKeys`	Yes	One or more audit rule key strings, e.g. "QueryMining_InefficientNGrams".
`accountId`	Yes	TrueClicks account id to retrieve results for (the numeric Id field from the account listing, not the platform customer id).
`campaignIds`	No	Optional campaign IDs to filter rows. Omit or leave empty to return all rows.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / accountId / description

Previous value: -"Ad platform account ID to retrieve results for."New value: +"TrueClicks account id to retrieve results for (the numeric Id field from the account listing, not the platform customer id)."

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral context beyond annotations: the exact JSONL block structure ('>>>>> RuleKey:' headers, a JSON Schema line with tooltips and column types, main rows with detail rows nested under 'children'), and the notable behavior that rules with no completed run in the last 30 days contribute no block.

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 dense and well-structured: verb+resource first, then output format, then use case, then the 30-day caveat. Every clause adds unique information—block structure, schema line contents, children nesting, raw-findings purpose, and the no-block condition—with no repetition or filler.

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 no output schema present, the description correctly carries the return-format burden and does so thoroughly (block structure, nesting, per-rule behavior). Minor gaps remain: block ordering across multiple rules, error behavior for invalid rule keys or account IDs, and row ordering are unspecified. For a 4-parameter tool with 100% schema coverage, this is near-complete.

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 the baseline is 3. The description loosely maps to parameters ('one account' → accountId, 'one or more rules' → ruleKeys) but adds no parameter-level detail beyond what the schema already provides. The schema itself carries the semantic load here.

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 states a specific verb+resource+scope: 'Get the detailed output rows for the latest completed audit run of one or more rules for one account.' The qualifier 'latest completed' and the 30-day window clearly distinguish this from the sibling audit_rule_output_table_historical, and the output format (multi-block JSONL) is specified in the first sentence.

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 description gives clear usage context: it provides 'the raw findings behind a failing audit rule' and applies to the 'latest completed audit run' with a 30-day window. However, it does not explicitly name alternatives (e.g., audit_rule_output_table_historical for older runs) or state when-not-to-use conditions, so it stops short of the explicit routing a 5 would require.

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

All TrueClicks 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?