Skip to main content
Glama

ADS Beast

seo_content_quality_audit

Read-only

An 80-criteria content quality audit (clarity, organisation, referenceability, experience, expertise, authority, trust) for a URL or a text. AI: 1 AI request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seo_content_quality_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNohttps:// page URL.
contentNoThe text, when there is no URL.
client_idNo
content_typeNoType of content, for weighting.blog_post

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds one genuinely new trait beyond that — the 'AI: 1 AI request' cost signal — but says nothing about latency, failure modes, or how page fetching behaves for the URL path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact fragments with zero filler and the core purpose front-loaded. However, the trailing 'AI: 1 AI request.' is presented as an unlabelled fragment rather than integrated information, which slightly hurts readability.

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?

With no output schema and zero required parameters, the description should say at minimum that at least one of url or content is needed and roughly what the audit returns (per-criterion scores vs. a single grade). Those gaps are real but not fatal for a read-only audit tool.

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 75%, so the schema carries most of the load. The description does usefully clarify that url and content are alternatives to each other, but adds nothing about client_id or how content_type changes the weighting beyond the schema's own 'for weighting' note.

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 and resource ('80-criteria content quality audit') plus the two input modes it accepts (URL or text) and the evaluated dimensions (clarity, organisation, referenceability, E-E-A-T). It is clearly distinguishable from a technical or on-page SEO audit sibling, though it never names the closest alternatives.

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 'for a URL or a text' phrasing implies the two entry conditions, but there is no explicit statement of when to pick this over seo_on_page_audit or aeo_content_optimize, nor any exclusion or prerequisite guidance.

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.