Skip to main content
Glama
Sign In
@gridwork/siteaudit

@gridwork/siteaudit

by thegridwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

audit_seo

Audit a website page's SEO elements including title, meta description, headings, Open Graph, Twitter Cards, canonical URL, and structured data to identify optimization opportunities.

Instructions

Check a page's SEO: title, meta description, headings, Open Graph, Twitter Cards, canonical URL, structured data, and more.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to audit for SEO

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description only lists what it checks without disclosing behavioral traits like read-only nature, rate limits, or handling of inaccessible pages.

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?

The description is a single sentence that efficiently enumerates SEO elements. It is not verbose, but could benefit from slightly more structure.

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?

Given the low parameter count and no output schema, the description adequately specifies the action. However, it omits details about the output format or response structure.

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% with a single parameter url. The description adds little beyond the schema description, so baseline 3 is appropriate.

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?

The description clearly states it checks a page's SEO and lists specific elements (title, meta description, headings, etc.), distinguishing it from siblings like audit_accessibility.

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?

The description implies usage for SEO auditing but provides no explicit guidance on when to use vs. alternatives like quick_check or audit_performance.

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