Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

Page size checker

ayrank_page_size
Read-only

Measure a URL's transferred and decoded size against Googlebot's 2 MB HTML limit (64 MB for PDF) and identify HTML sections or inline assets pushing it past the cut.

Instructions

Use to measure a URL's transferred and decoded size against Googlebot's 2 MB limit (64 MB for PDF), and for HTML see what sits past the cut and which parts (inline scripts, JSON, Next.js payload, styles, svg) take the bytes. Linked CSS, scripts and images are not fetched. No ranking claim. Free AY Rank API, no key. JavaScript is not run, so content added by scripts is not seen.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe page or file to measure, like https://example.com/page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight and does so: it discloses that linked subresources are not fetched, JavaScript is not executed, script-injected content is invisible, and no API key is needed. Those are exactly the behavioral facts that change how an agent should interpret the result versus a browser render.

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?

Purpose is front-loaded in the first clause, and each following clause carries distinct information: limits, output breakdown, fetch exclusions, no-ranking disclaimer, API access, JS caveat. Nothing is repeated from the name or schema and no sentence is filler.

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?

With no output schema, the description does the work of describing what comes back (transferred vs decoded size, over-limit content, per-category byte attribution) and states its measurement limits. What it lacks is any sense of response shape or units, which an agent would still have to discover on the first call.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains the URL input. The description usefully signals that non-HTML files (PDF, with a 64 MB limit) are acceptable values, but adds no format, normalization, or encoding guidance beyond that.

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 opens with a specific verb and resource ('measure a URL's transferred and decoded size') and immediately scopes it against concrete limits (2 MB Googlebot, 64 MB PDF). It also names the HTML byte breakdown it returns (inline scripts, JSON, Next.js payload, styles, svg) and explicitly disclaims ranking ('No ranking claim'), which cleanly separates it from ranking-oriented siblings such as ayrank_title_score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear when-to-use framing ('Use to measure...') plus exclusionary context: linked CSS/scripts/images are not fetched, JavaScript is not run, and it makes no ranking claim. It does not name a specific sibling tool to use instead when the agent actually wants ranking or fetch-behavior signals, so it stops short of full alternative routing.

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