Skip to main content
Glama

ADS Beast

seo_on_page_audit

Read-only

One page audited across title, meta description, headings, content, keywords, internal links, images and technical basics. AI: 1 AI request.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttps:// page URL.
keywordNoTarget search query.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint true, openWorldHint true, destructiveHint false), so the bar is lower. The description's real contribution is the cost disclosure 'AI: 1 AI request', which is genuinely useful for an agent budgeting calls, though the cryptic fragment could have explained consumption more clearly. It says nothing about the form or size of the response or about rate limits.

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?

Two short telegraphic sentences with zero filler, and the scope statement is front-loaded. The clipped 'AI: 1 AI request' fragment is efficient but reads as jargon rather than prose.

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 must convey what comes back; listing the audited areas partially does that, but an agent still cannot tell whether the result is a score, a findings list, or pass/fail per section. With three parameters and one, client_id, undocumented anywhere, the definition is only adequate for its complexity.

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 description coverage is 67%, so the url and keyword parameters are already documented in the schema. The description only reinforces 'one page' (mapping to url) and mentions 'keywords' in the list, without explaining how keyword affects scoring, and says nothing about client_id, which is undocumented in both places.

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?

A concrete verb ('audited') plus a precise scope ('One page') and an explicit enumeration of what is checked (title, meta description, headings, content, keywords, internal links, images, technical basics). It does not differentiate from siblings such as seo_content_quality_audit, seo_internal_links_audit or seo_technical_audit, even though the listed coverage overlaps heavily with them.

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 phrase 'One page' implicitly scopes the tool to a single URL rather than a site or domain, which is some usable guidance. But it never says when to pick this broad audit over the narrower sibling audits, nor any prerequisite about having a URL versus a keyword in hand.

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.