Skip to main content
Glama

OnPage.dev

by dev.onpage
OverviewDiscussionsAdmin

Share and export

share

Send results where the team works. Pick with mode: link = A link to the visual report. Needs url. export = A Google Sheet, CSV, Slack message or one task per issue.

Input Schema

NameRequiredDescriptionDefault
urlNoFull address, for example https://example.com/pricing.
modeNoDefault link.
detailNobrief = short summary.
audit_idNoA finished site audit from start_site_audit, to export the whole site.
memory_keyNosite_memory key, records this call.
slack_webhook_urlNoOptional https incoming webhook (Slack, Discord, Teams) to post the summary to.

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. Changed2 schema fields changed
    • 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."
  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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful context about external side effects (creating a Google Sheet, CSV, Slack message, or one task per issue) and the url dependency for link mode, but says nothing about repeat-call behavior, auth needs, or rate limits despite idempotentHint=false.

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?

Three short sentences that are front-loaded with the overall purpose before the mode breakdown. Nearly every clause carries information, though 'Send results where the team works' is slightly promotional 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?

An output schema exists so return values need not be explained, and the six parameters are fully documented in the schema. The description covers the two operationally important knobs (mode and url) but omits any mention of detail, audit_id, memory_key, or slack_webhook_url beyond what the schema already provides.

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 description coverage is 100%, so a baseline of 3 is warranted, but the description goes beyond the terse schema text by explaining what each mode value actually produces and by flagging that link mode additionally requires url. That extra meaning exceeds the schema's 'Default link.'

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 names a specific verb (send/share) and resource (results/reports) and splits the tool into two named modes with link and export outputs. It is clear what the tool does, though it does not directly contrast itself with sibling analysis tools like dashboard or site_audit.

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?

It gives conditional guidance for choosing a mode ('link = A link to the visual report. Needs url', 'export = A Google Sheet, CSV...'), which routes the agent reasonably well. However, there is no explicit when-not-to-use, no prerequisites, and no mention of alternatives among the many sibling tools.

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