Skip to main content
Glama

Run site audit

run-site-audit

Queue a site health audit of the tracked page ids given from list-site-pages or, when page_ids is omitted, of up to 50 tracked pages. Each page uses one unit of the site audit quota, and the request is refused past the quota. Audits run in the background; results appear in list-site-audits. Returns the queued audit ids. Confirm with the user before auditing many pages.

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": {
      "domain_id": "<domain_id>"
    },
    "name": "run-site-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idsNoUp to 200 tracked page IDs from list-site-pages; omit for up to 50 tracked pages
domain_idYesDomain ID from list-domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / page_ids / description
      Previous value: -"Tracked page IDs from list-site-pages; omit for up to 50 tracked pages"New value: +"Up to 200 tracked page IDs from list-site-pages; omit for up to 50 tracked pages"
    • addedInput schema / properties / page_ids / maxItems
      Added value: +200
  2. Changed2 schema fields changed
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
    • changedInput schema / properties / page_ids / description
      Previous value: -"Specific page IDs to audit (omit for all tracked pages)"New value: +"Tracked page IDs from list-site-pages; omit for up to 50 tracked pages"
  3. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedInput schema / properties / page_ids / items / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the quota model (one unit per page), that requests are refused past quota, that execution is asynchronous in the background, where results surface, and what is returned (queued audit ids). This combination of cost, failure condition, and async semantics is exactly the kind of behavior an agent cannot infer from destructiveHint=false and openWorldHint=true.

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?

Four tight sentences, front-loaded with the action and scope, followed by cost, async behavior, return value, and a safety caveat. Every sentence adds operational information; nothing restates the title or annotations.

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?

Although there is no output schema, the description states what is returned (queued audit ids) and where results appear later, and it covers quota limits and the async lifecycle. For a two-parameter queueing tool, an agent has everything needed to invoke it correctly and handle failure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by tying page_ids to its source (list-site-pages), explaining the omission default, and attaching quota cost per page — meaning the schema text alone does not convey. The 200-item schema cap versus the 50-page default is not explicitly reconciled, but the two are not contradictory.

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 ('Queue a site health audit') plus the exact scope (given page ids, or up to 50 tracked pages when omitted). It names the sibling tools that supply inputs (list-site-pages) and results (list-site-audits), so it is distinguishable from list-site-audits and get-audit-issues without opening a schema.

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?

Gives clear context: call it after list-site-pages, omit page_ids for a default sweep, read output via list-site-audits, and confirm with the user before auditing many pages. It does not explicitly say when not to run an audit versus using get-site-health-summary or get-audit-issues, so it falls just short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources