Skip to main content
Glama

OnPage.dev

by dev.onpage
OverviewDiscussionsAdmin

Ready-to-paste fixes

get_fix_pack
Read-onlyIdempotent

Generate ready-to-paste fixes for the issues on a page, built from the page's own content: a title tag, meta description, canonical, social (Open Graph) tags, viewport and a JSON-LD starting point. Only issues the page actually has are included. With platform wordpress it returns a WordPress plan instead: the exact Yoast SEO or Rank Math field for each value, alt texts for the media library, and the steps to ship it through the user's own WordPress connection (for example a WordPress MCP server) after the user approves each change. With platform git it returns the fixes as code for the site's framework (Next.js, Nuxt, SvelteKit, Astro, Angular, React, Vue or plain HTML, detected from the page) and the steps to ship them as a pull request on a new branch, checked with scan_html before the user merges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull address of the page, for example https://example.com/pricing. A bare domain like example.com also works.
platformNohtml (default) for code to paste, wordpress for a plan your WordPress connection can apply, git for framework code and the steps to open a pull request.
frameworkNoWith platform git: the site's framework. auto (default) detects it from the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / framework
      Added value: +{
+  "description": "With platform git: the site's framework. auto (default) detects it from the page.",
+  "enum": [
+    "auto",
+    "nextjs-app",
+    "nextjs-pages",
+    "nuxt",
+    "sveltekit",
+    "astro",
+    "angular",
+    "react",
+    "vue",
+    "html"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / platform / description
      Previous value: -"html (default) for code to paste, wordpress for a plan your WordPress connection can apply."New value: +"html (default) for code to paste, wordpress for a plan your WordPress connection can apply, git for framework code and the steps to open a pull request."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "html",
-  "wordpress"
-]New value: +[
+  "html",
+  "wordpress",
+  "git"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "html (default) for code to paste, wordpress for a plan your WordPress connection can apply.",
+  "enum": [
+    "html",
+    "wordpress"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds real workflow context beyond that: only issues the page actually has are emitted, WordPress changes require per-change user approval, and git output is a PR on a new branch gated by scan_html. It does not cover auth or rate limits, but for a read-only generator this is strong.

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?

Front-loaded with the core purpose, but the first sentence is a long run-on enumerating six artifacts and the platform branches are delivered as dense prose that overlaps with the schema's enum descriptions. Every sentence carries information, yet the packaging makes it harder to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the full burden of describing returns, and it does: it describes the artifact bundle for html, the field-level plan for wordpress, and the framework code plus PR steps for git. An agent has enough to call it correctly and anticipate the response shape.

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, but the description adds meaning the schema does not: it spells out the downstream consequence of each platform value and notes that framework auto-detection only applies with platform git.

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 ('generate ready-to-paste fixes') and enumerates exactly what is produced (title tag, meta description, canonical, OG tags, viewport, JSON-LD), then branches on platform. It is clearly distinguishable from siblings like prioritize_fixes (which ranks, not generates) and generate_schema (single artifact, this builds a bundle).

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?

Explains the conditions that select each mode (platform html/wordpress/git) and names a downstream step (scan_html before merge, user approval per change). It stops short of saying when to prefer prioritize_fixes or generate_schema instead.

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