Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

45-Point Technical SEO, Schema & Broken Link Auditor

audit_technical_seo_broken_links
Read-onlyIdempotent

Audit any URL for technical SEO issues, broken links, JSON-LD Schema.org, OpenGraph tags, and security headers to identify fixes that improve search visibility and page quality.

Instructions

Run a 45-point technical SEO, broken link, JSON-LD Schema.org, OpenGraph, and security header audit on any URL ($0.80/1k).

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": {
      "urls": "<urls>"
    },
    "name": "audit_technical_seo_broken_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesFull webpage URLs to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value annotations do not carry: the price ($0.80/1k) and the audit breadth ('45-point', naming the specific check categories). It stops short of disclosing output shape, per-URL failure behavior, or rate/throughput limits.

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?

One front-loaded sentence with the action, the scope of checks, the target, and the cost. Nothing is redundant and no sentence is filler.

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?

There is no output schema, so the description is the only place to learn what comes back from an audit, and it says nothing about results (findings list, pass/fail counts, severity). For a broad read-only audit tool with one parameter and strong annotations, this is the main remaining gap.

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 the single parameter is already documented as 'Full webpage URLs to audit', so the schema does the heavy lifting. The description's 'on any URL' plus per-1k pricing hints that the array is the billing unit and should be batched, but adds no format or validation detail beyond the schema.

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?

States a specific verb ('Run ... audit') and resource ('any URL') and enumerates the check families covered: technical SEO, broken links, JSON-LD Schema.org, OpenGraph, security headers. That is far more specific than any sibling (lead-scraping and funnel-spy tools), though it never explicitly names what it is not.

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?

Usage is only implied: an agent infers you call this when you have page URLs and want a technical SEO/diagnostic sweep. There is no statement of when to prefer a different tool, no prerequisite or eligibility notes, and no guidance on whether this substitutes for or complements a page-content tool.

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