Skip to main content
Glama

microlink

by io.github.pipeworx-io

Take Screenshot

take_screenshot
Read-onlyIdempotent

Capture a screenshot of any webpage. Returns image URL showing the rendered page layout and visual content—use to verify page state or design.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the webpage to screenshot.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoThe URL that was screenshotted
widthNoScreenshot width in pixels
heightNoScreenshot height in pixels
screenshot_urlNoURL of the generated screenshot image

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "height": {
+      "description": "Screenshot height in pixels",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "screenshot_url": {
+      "description": "URL of the generated screenshot image",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "The URL that was screenshotted",
+      "type": "string"
+    },
+    "width": {
+      "description": "Screenshot width in pixels",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://www.example.com"
+  },
+  {
+    "url": "https://www.wikipedia.org"
+  }
+]
  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 destructiveHint=false, so the safety profile is clear. The description adds valuable context beyond annotations by specifying the return format (image URL) and the nature of content (rendered page layout and visual content), helping the agent understand what to expect.

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?

The description is a single, well-structured sentence that front-loads the action and includes all necessary details without any fluff. Every clause contributes meaning.

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?

For a simple, read-only tool with one parameter, complete annotations, and an output schema, the description covers purpose, return value, and use case. It is fully sufficient for an agent to select and invoke the tool correctly.

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?

The schema provides 100% coverage for the single 'url' parameter with a clear description. The tool description does not add significant detail beyond the schema, but it reinforces the 'any webpage' scope. Since the schema does the heavy lifting, a baseline of 3 is appropriate.

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?

The description clearly states the specific action ('Capture a screenshot'), the resource ('any webpage'), and the return value ('image URL showing the rendered page layout and visual content'). It is unambiguous and distinct from any sibling tools, none of which relate to screenshots.

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?

Provides a clear use case: 'use to verify page state or design.' It does not mention explicit alternatives or exclusions, but none are needed given the absence of similar sibling tools. The context is sufficiently clear to know when to invoke it.

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

All microlink toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes with detailed usage guidance, but the several query entry points (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) overlap conceptually and require careful reading to select correctly. Notably, ask_pipeworx_beta currently behaves identically to ask_pipeworx, which could cause confusion.

Naming Consistency3/5

Tool names mix verb-first (remember, resolve_entity) and noun-first (entity_profile, deep_research) patterns, with some using prefixes like 'polymarket_' or 'ask_pipeworx'. While all are snake_case and readable, the lack of a single consistent convention makes the set feel less coherent than it could be.

Tool Count3/5

33 tools is on the high end for a single server, though the broad domain (data retrieval, prediction markets, memory, subscriptions, web scraping) justifies much of the sprawl. Still, the count borders on heavy, and some tools could potentially be consolidated (e.g., the ask_pipeworx variants).

Completeness4/5

The toolset provides comprehensive coverage for its core data querying and analysis domain, with lifecycle coverage for memory and subscriptions. Minor gaps exist, such as no generic 'fetch page content' tool despite having get_metadata and take_screenshot, but these do not undermine the primary functionality.

Resources