Skip to main content
Glama
Sign In

Bannerproof

by app.bannerproof
OverviewDiscussionsAdmin

Audit several websites (1 credit each)

audit_domains
Destructive

Audits up to 10 websites at once (e.g. an agency's client list or prospects). Spends 1 audit credit per new audit and runs only with confirm=true; sites audited in the last 24 hours are reused without spending. If the account doesn't have enough credits for the whole list, nothing starts (no partial batch). A site that can't be scanned (down, blocking bots, too slow) is not charged — its credit is returned automatically. Returns a job_id per site — follow up with get_audits_status for all of them, then get_findings per domain.

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": {
      "domains": "<domains>",
      "confirm": "<confirm>"
    },
    "name": "audit_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesConfirms spending 1 audit credit per new audit; without true nothing runs
domainsYesThe websites' domains, e.g. ["client-a.com", "client-b.de"] — up to 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domains / description
      Previous value: -"The websites' domains, e.g. [\"client-a.com\", \"client-b.de\"] — up to 20"New value: +"The websites' domains, e.g. [\"client-a.com\", \"client-b.de\"] — up to 10"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/openWorldHint annotations by disclosing the full cost model: 1 credit per new audit, 24-hour cache reuse at no charge, all-or-nothing credit check with no partial batch, and automatic credit return for unscannable sites. These are exactly the consequences an agent needs before invoking a destructive, credit-spending batch operation.

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?

Front-loads the core action and batch size, then layers cost, failure, and follow-up behavior in logical order with no filler sentences. It is on the longer side, but nearly every clause carries operational information.

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 destructive, open-world batch mutation with no output schema, the description covers everything an agent needs: cost, gating, atomicity, refund behavior, the job_id return value, and the downstream tool chain. No significant gap remains.

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 both parameters are already documented, including the confirm gating and the 10-domain cap. The description restates the confirm requirement and adds a batch-size reminder, but no new syntax or format guidance beyond the 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 resource ('Audits up to 10 websites at once') with an explicit batch size, which cleanly separates it from the single-site audit_domain and the lighter quick_check/scan_domain siblings. An agent knows immediately this is the bulk-audit entry point.

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

Usage Guidelines5/5

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

Gives a concrete usage scenario ('an agency's client list or prospects'), states the hard precondition (runs only with confirm=true), and describes the post-call workflow — use get_audits_status for the returned job_ids, then get_findings per domain. That is explicit when-to-use plus named follow-up tools.

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

All Bannerproof 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