Skip to main content
Glama

launchfiles_seo_audit

Read-onlyIdempotent

Run or recall LaunchFiles' Search & SEO Radar: live Search Console CTR-leak prioritization, sitemap crawl on up to 10 routes, SERP landscape, and cross-model claim-verified upgrade package.

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": "launchfiles_seo_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDomain or live https:// URL to audit.
modeNofull_audit (default) runs a fresh crawl+author+verify pass; memory_only returns persisted domain history.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds a real operational constraint ('up to 10 routes') and lists what the run produces, which is meaningful since there is no output schema. It still omits runtime expectations, Search Console auth requirements, and whether a fresh crawl is costly or rate-limited.

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 sentence with the verb front-loaded and zero filler. It is dense with comma-separated feature claims rather than layered explanation, but nothing is wasted or repeated.

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?

For a two-parameter, fully documented, annotation-covered audit tool with no output schema, the description carries enough: it names the inputs' purpose and enumerates the deliverables an agent would receive. Only the operational cost/auth picture is thin.

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 coverage is 100% and both parameters are already documented there, including the mode enum values in prose. The description's 'Run or recall' and route-limit phrasing loosely mirrors those parameters but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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?

Opens with a specific verb+resource pairing ('Run or recall LaunchFiles' Search & SEO Radar') and enumerates the concrete outputs (CTR-leak prioritization, sitemap crawl on up to 10 routes, SERP landscape, claim-verified upgrade package). An agent can tell this is the SEO audit tool rather than an indexing, UX, or drift check, though the sibling differentiation is implicit in the domain naming rather than stated.

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

Usage Guidelines3/5

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

'Run or recall' hints at the two modes, and the schema spells out full_audit vs memory_only, but the description never says when to prefer this over launchfiles_ux_audit or launchfiles_live_drift_check, nor any prerequisites. Usage is inferable from the feature list, not directed.

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.