Skip to main content
Glama
webEmbedding

webEmbedding

by jongko54

audit_reference_url

Read-onlyIdempotent

Checks a URL before cloning or embedding to determine if the page can be reused as-is, needs browser capture or login, requires manual review, or should be blocked—and returns the next tool to call.

Instructions

Preflight check before cloning or embedding a URL, without launching a browser. Returns whether the page can be reused/embedded as-is, needs local browser capture, needs a logged-in session, needs manual review, or should be blocked, plus the next tool to call.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the page to inspect, capture, or clone.
license_textNoLicense or permission text that allows reusing the page, from the user or the site; informs the reuse/rebuild policy.
source_signalsNoExtra hints about the page's origin, e.g. ["framer", "spline", "export"]; merged with signals detected from the page.
exact_requestedNoTrue (default) when the user wants an exact, faithful clone; false when an approximate rebuild is acceptable.
timeout_secondsNoTimeout in seconds for the static HTTP fetch of the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.13
    • addedInput schema / properties / exact_requested / description
      Added value: +"True (default) when the user wants an exact, faithful clone; false when an approximate rebuild is acceptable."
    • addedInput schema / properties / license_text / description
      Added value: +"License or permission text that allows reusing the page, from the user or the site; informs the reuse/rebuild policy."
    • addedInput schema / properties / source_signals / description
      Added value: +"Extra hints about the page's origin, e.g. [\"framer\", \"spline\", \"export\"]; merged with signals detected from the page."
    • addedInput schema / properties / timeout_seconds / description
      Added value: +"Timeout in seconds for the static HTTP fetch of the page."
    • addedInput schema / properties / url / description
      Added value: +"Public http(s) URL of the page to inspect, capture, or clone."
  2. First observedv0.3.12

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the no-browser static-fetch behavior and the five-way outcome taxonomy plus a recommended next tool — genuinely useful routing context. It does not mention what happens on fetch failure or how license_text affects the verdict beyond the schema.

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?

One front-loaded sentence that begins with the purpose and ends with the return shape; no filler. The enumerated outcome list makes the sentence long, but each clause adds information an agent needs.

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 correctly takes on the job of describing return values via the outcome categories and next-tool pointer. For a read-only, single-URL preflight tool this is nearly sufficient; only error/failure behavior and timeout implications are left implicit.

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?

Schema description coverage is 100%, so every parameter is already documented, and the description adds no parameter-level detail. Baseline 3 applies when the schema carries the semantic load.

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?

States a specific verb ('preflight check') and resource ('a URL'), plus a clear scope constraint ('without launching a browser') that separates it from capture_reference_bundle or clone_reference_url. It enumerates the verdict categories the tool produces, so an agent knows exactly what decision it gets back, though no sibling is named outright.

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?

The phrase 'Preflight check before cloning or embedding a URL' gives a clear call point in the workflow, and 'without launching a browser' signals a cheap first step before heavier capture tools. It stops short of naming the alternative tools (inspect_url, classify_clone_mode) or stating when to skip this check.

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