Skip to main content
Glama

run_audit

Runs a GEO visibility audit for a URL, checks robots.txt, sitemaps, metadata, schema, and AI discovery files, then generates prioritized fixes and a Markdown report.

Instructions

运行 GEO 可见度诊断并生成 Markdown 报告。

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": {
      "url": "<url>"
    },
    "name": "run_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes完整的 http:// 或 https:// URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the meaningful fact that the result is a Markdown report rather than structured data (important since there is no output schema), but it says nothing about whether the URL is fetched live, how long the audit takes, rate limits, or failure behavior.

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?

A single short sentence with zero filler, and the action is front-loaded ahead of the deliverable. It is not bloated, though it is arguably too terse for a diagnostic tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no annotations and no output schema, the description covers the core action and the deliverable format. It leaves gaps around what the diagnosis actually inspects, what the report contains, and runtime/network behavior.

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?

There is a single parameter and the schema already documents it fully (100% coverage, '完整 http:// 或 https:// URL'). The description adds no extra meaning, which is acceptable given the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and target (run a GEO visibility diagnosis) and adds the concrete artifact it produces (a Markdown report). It is distinguishable from siblings like check_meta/check_robots/check_sitemap, which are single-aspect checks, but the description never explicitly states that distinction.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over the narrower sibling checks, no prerequisites, and no exclusions. An agent must infer that this is the broader/aggregate diagnostic purely from the words 'GEO 可见度诊断'.

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

Deploy Server

Other Tools