Skip to main content
Glama

Request a site audit

request_site_audit
Idempotent

Queues a crawl audit of the property's own site in Organiq (HTML pages inside the verified property, robots.txt respected). Answers status "queued", or "not_queued" with reason "already_open" (an audit is queued or running) or "recent" (the last audit finished less than 24 hours ago), with the date of the last audit. The audit finishes within minutes to some hours depending on site size; read the result with get_site_audit. Writes only to Organiq, never to the audited site, Search Console, GA4 or Bing. Needs the write scope (mcp:write). Use it when get_site_audit reports no audit yet or the user fixed issues and wants a new reading. / Põe uma auditoria do site na fila; recusa se já há uma aberta ou se a última tem menos de 24 h.

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": {
      "site": "<site>"
    },
    "name": "request_site_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesProperty: displayName ("example.com"), Search Console siteUrl ("sc-domain:example.com", "https://www.example.com/") or numeric id. A unique substring among visible properties also works ("exam"). list_sites shows the options. The value "demo" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; "demo" é um site de demonstração com dados fictícios, sem login e só leitura.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description goes well beyond them: it discloses the 24-hour cooldown, the exact status vocabulary returned, the asynchronous duration ("minutes to some hours"), the required mcp:write scope, and that writes touch only Organiq and never the audited site, Search Console, GA4 or Bing. That last point is exactly the reassurance an agent needs before calling a non-destructive write.

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-loaded with the action, then statuses, then timing, then scope, then usage — a sensible ordering with no filler. The trailing Portuguese restatement duplicates content already given in English, which is slightly redundant but appears to be a deliberate bilingual convention.

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?

No output schema exists, and the description fully compensates by enumerating the possible return statuses and their reasons plus the last-audit date. Combined with the timing estimate and the pointer to get_site_audit for results, an agent has everything needed to call this correctly and set expectations.

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?

With one parameter at 100% schema coverage, the schema already documents accepted forms (displayName, siteUrl, numeric id, unique substring, and the read-only "demo" value). The description only reinforces that the site must be the property's own site, adding marginal meaning beyond the schema — the 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?

States a specific verb and resource — "Queues a crawl audit of the property's own site in Organiq" — and immediately scopes it to HTML pages inside the verified property with robots.txt respected. This makes it trivially distinguishable from the read-side sibling get_site_audit, which is named explicitly.

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 both the when-to-use condition ("when get_site_audit reports no audit yet or the user fixed issues and wants a new reading") and the when-not conditions (already_open, recent — last audit under 24 hours ago). The reader is routed to get_site_audit for results, so the write/read split is unambiguous.

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.