OnPage.dev

Fix log

fix_log

Record shipped fixes, keep them live and report on them. Pick with mode: log = Record a shipped fix; checked every 6 hours, restore code on regression. Needs fixes[{url, field, new, old, via, ref}]. report = Every fix with status and results: a monthly client report. Needs fix_log_id.

Input Schema

Name	Required	Description
`mode`	No	Default log.
`brand`	No	For the report: your agency name for the header.
`fixes`	No
`month`	No	For the report: YYYY-MM.
`detail`	No	brief = short summary.
`format`	No	status (default), a client report, or GA4 annotations (one per ship date) for the Admin API.
`verify`	No	Check the live pages now (4 pages per call).
`webhook`	No	Optional https URL (Slack, Discord, Zapier, n8n, a GitHub Action) that gets the restore code when a fix is undone.
`fix_log_id`	No	Add to an existing log.
`memory_key`	No	site_memory key, records this call.
`shipped_at`	No	Date the fixes went live, YYYY-MM-DD.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

removedOutput schema / description

Removed value: -"The result as structured data; fields depend on mode."

Changed2 schema fields changedOct 13, 2026

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."

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "brief returns a short summary, default full.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / memory_key

Added value: +{
+  "description": "Optional site_memory key, to record this call in the site memory.",
+  "maxLength": 80,
+  "type": "string"
+}

AddedOct 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (which only say not-read-only, open-world, non-idempotent, non-destructive), the description discloses real behavior: fixes are re-checked every 6 hours and code is restored on regression, the webhook receives restore code when a fix is undone, verify checks live pages at 4 pages per call, and format=annotations emits GA4 Admin API annotations. Auth/permission requirements are not covered, keeping it at 4.

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?

Front-loaded purpose followed by two clearly labeled mode branches; nothing reads as filler and the per-branch prerequisite lists are compact. The bracketed "fixes[{url, field, new, old, via, ref}]" shorthand is terse but functional rather than elegant.

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 11 parameters at 91% schema coverage and an output schema present, the description does the work that matters: mode selection, branch prerequisites, verification cadence, and webhook notification behavior. Only authentication/authorization context and the relationship to sibling monitoring tools are absent.

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 91%, so the baseline is 3, but the description adds mode-scoped meaning the flat schema does not convey: which parameters belong to the log branch (fixes subfields url/field/new/old/via/ref) versus the report branch (fix_log_id), plus the 6-hour check semantics tied to the logged values. Minor tension exists between the schema's "Add to an existing log" phrasing for fix_log_id and the description presenting it as required for report mode.

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 opening sentence states a specific verb and resource ("Record shipped fixes, keep them live and report on them") and the mode branch spells out both operations, so the agent knows exactly what the tool does. It does not, however, name or contrast any sibling (e.g. watch, tracking, site_memory), so it falls short of the 5-level sibling differentiation bar.

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?

"Pick with mode: log = ... report = ..." gives explicit branch conditions, and the "Needs fixes[...]" / "Needs fix_log_id" clauses state which inputs each branch requires. There is no when-not guidance and no named alternative tool, so it stops short of 5.

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

All OnPage.dev tools Inspect

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.