Skip to main content
Glama
Sign In
markfetch-mcp

markfetch-mcp

by asdfas988
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

screenshot_url

Capture a web page as a PNG screenshot, converting a URL into visual data for AI agents to analyze.

Instructions

Capture a screenshot of a web page as a PNG image.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe web page URL to screenshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only mentions the output format (PNG). It does not cover rendering behavior, page load handling, viewport settings, rate limits, or any side effects, leaving a significant transparency 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?

The description is a single sentence with no redundant words. It is concise, front-loaded, and every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimally viable for a simple one-parameter tool, covering purpose and output format. However, it lacks behavioral context such as usage alternatives, rendering specifics, and potential limitations, making it less complete than it could be.

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 input schema fully documents the 'url' parameter with 100% coverage. The description adds no extra meaning beyond what the schema already states, so the baseline score of 3 applies.

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 tool captures a screenshot of a web page as a PNG image. The verb 'Capture' and resource 'screenshot of a web page' are specific, and the mention of PNG distinguishes it from the sibling tool 'scrape_url'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool over alternatives like 'scrape_url'. There are no exclusions, prerequisites, or contextual hints about when it is appropriate.

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