Skip to main content
Glama

OnPage.dev

by dev.onpage
OverviewDiscussionsAdmin

Compare

compare
Read-only

Compare pages side by side. Pick with mode: pages = Your page against up to 3 competitors. Needs url, competitors. html = Two versions of HTML before and after. Needs before, after. preview = Deploy preview against production before merging. Needs preview_url, production_url.

Input Schema

NameRequiredDescriptionDefault
urlNoFull address, for example https://example.com.
modeNoDefault pages.
afterNoHTML after the change.
pathsNoPaths like /pricing, default /.
beforeNoHTML before the change.
detailNobrief = short summary.
keywordNoOptional search term to compare keyword use.
memory_keyNosite_memory key, records this call.
competitorsNoCompetitor page addresses.
preview_urlNoThe deploy preview URL.
bypass_tokenNoVercel protection bypass secret.
production_urlNoThe live site.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / description
      Removed value: -"The result as structured data; fields depend on mode."
  2. Changed7 schema fields changed
    • addedInput schema / properties / bypass_token
      Added value: +{
+  "description": "Vercel protection bypass secret.",
+  "maxLength": 200,
+  "type": "string"
+}
    • changedInput schema / properties / detail / description
      Previous value: -"brief returns a short summary, default full."New value: +"brief = short summary."
    • changedInput schema / properties / memory_key / description
      Previous value: -"Optional site_memory key, to record this call in the site memory."New value: +"site_memory key, records this call."
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "pages",
-  "html"
-]New value: +[
+  "pages",
+  "html",
+  "preview"
+]
    • addedInput schema / properties / paths
      Added value: +{
+  "description": "Paths like /pricing, default /.",
+  "items": {
+    "maxLength": 2048,
+    "type": "string"
+  },
+  "maxItems": 5,
+  "type": "array"
+}
    • addedInput schema / properties / preview_url
      Added value: +{
+  "description": "The deploy preview URL.",
+  "maxLength": 2048,
+  "type": "string"
+}
    • addedInput schema / properties / production_url
      Added value: +{
+  "description": "The live site.",
+  "maxLength": 2048,
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "brief returns a short summary, default full.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / memory_key
      Added value: +{
+  "description": "Optional site_memory key, to record this call in the site memory.",
+  "maxLength": 80,
+  "type": "string"
+}
  5. Added

TDQS

A4.4/5.0
Behavior4/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 mode-dependent behavior and per-mode input requirements, which goes beyond the annotations, though it says nothing about permissions, rate limits, or what the comparison returns.

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?

Front-loaded with the core purpose, then a tight one-line-per-mode breakdown. Every clause carries information; there is no 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 an output schema present the description need not explain return values, and annotations cover the safety profile. The mode/parameter mapping makes the 12-parameter tool navigable, though optional params like paths, detail, keyword, and memory_key are left to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds genuine value beyond the schema by grouping parameters per mode (url+competitors for pages, before+after for html, preview_url+production_url for preview), which the flat schema does not express.

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?

States a specific verb and resource ("Compare pages side by side") and then enumerates the three modes with a concrete description of each comparison. An agent can tell exactly what the tool does and how the three variants differ without opening the schema.

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?

Explicitly maps each mode to a scenario (pages = you vs competitors, html = before/after versions, preview = deploy preview vs production) and names the parameters each mode requires. It stops short of naming when not to use the tool or alternatives among siblings, but the mode-routing guidance is strong.

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

All OnPage.dev toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources