Skip to main content
Glama
Agency MCP Server

Agency MCP Server

Page audit

audit_page
Read-only

Runs an on-page audit of one URL, checking title, meta description, canonical, language, headings, links, image alt text, and Open Graph tags, then reports issues by severity.

Instructions

On-page audit of one URL: title, meta description, canonical, lang, heading structure, links, image alt text and Open Graph tags, with issues by severity.

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": {
      "client": "<client>",
      "url": "<url>"
    },
    "name": "audit_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL inside the client's allowlist.
clientYesClient id from the server's config (dental, cafe, plumber).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.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=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds what gets checked and that results are 'issues by severity', but does not disclose live-fetch behavior, allowlist enforcement, rate limits, or error modes beyond what the schema says about the allowlist.

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?

A single front-loaded sentence that enumerates the audit surface and ends with the output summary. Every clause carries information and there is no 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?

With no output schema, the description carries more of the return-value burden; it hints at 'issues by severity' but does not describe the response structure. For a read-only two-parameter audit this is adequate but leaves an agent guessing about the shape of results.

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 100% and both parameters (url, client) are well documented in the schema. The description adds no parameter-level meaning, which is the baseline expectation at full coverage.

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?

The description gives a specific verb+resource ('On-page audit of one URL') and enumerates exactly what is inspected (title, meta, canonical, headings, links, alt text, OG tags), which makes it clearly distinct from a multi-page crawl. It stops short of naming a sibling, so it lands at 4 rather than 5.

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 by 'one URL': an agent can infer this is for single-page inspection rather than site-wide crawling, but there is no explicit when-to-use, when-not, or alternative routing guidance.

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