Skip to main content
Glama
Sign In
Unilytics MCP Server

Unilytics MCP Server

Official
by TeamUnilytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

js_scrape

Read-only

Scrape JavaScript-rendered pages by waiting for SPAs and dynamic content to load, then extract rendered SEO audit signals such as titles, meta tags, headings, structured data, and issues.

Instructions

Scrape a JavaScript-rendered page (SPAs, React, Vue, Angular apps).

Unlike the standard scrape, this waits for JavaScript to fully execute
before extracting content. Use this for single-page applications, dynamic
content, or any page where content loads via JS.

Returns full SEO audit signals from the rendered HTML: title, meta tags,
headings, Open Graph, structured data, canonical, images, and issues.

Args:
    url: Full URL to scrape (e.g. "https://app.example.com")
    wait_for: Milliseconds to wait for JS to render (default: 5000, max: 15000)

[Provider: Firecrawl]

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

Input Schema

NameRequiredDescriptionDefault
urlYes
wait_forNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / config
      Removed value: -{
-  "default": null,
-  "title": "config",
-  "type": "string"
-}
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world, so the safety profile is covered. The description adds real behavioral context beyond that: it waits for JS execution before extraction and documents the wait default and 15000ms ceiling. It doesn't mention timeouts, failure modes, or rate/cost limits, which is the remaining gap.

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 one-line purpose, then the differentiation, then return contents, then args. Each section earns its place and nothing is repeated from the schema beyond the useful default/max values.

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?

For a two-parameter tool with no output schema, it adequately covers what comes back (SEO audit signals: title, meta, headings, OG, structured data, canonical, images, issues) and the timing knob. Provider attribution is a small bonus; error behavior on timeout is the only notable omission.

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 0%, so the description carries the full burden and does so: 'url' includes an example format and 'wait_for' explains units (milliseconds), default (5000) and maximum (15000). Only the URL validation rules (scheme, http vs https) are left unspecified.

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 ('Scrape a JavaScript-rendered page') and immediately scopes it to SPAs / React / Vue / Angular, which separates it from the static content_scrape sibling. The contrast with 'the standard scrape' makes the distinction unambiguous.

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 says when to use it ('single-page applications, dynamic content, or any page where content loads via JS') and points to the non-JS alternative implicitly via 'Unlike the standard scrape'. It doesn't name the sibling tool exactly or state a when-not case, which keeps it out of the top band.

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

Deploy Server

Other Tools