Skip to main content
Glama

Argoshot

Read a web page as Markdown

page_to_markdown
Read-onlyIdempotent

Loads a public page in a real browser (scripts run) and returns its content as Markdown. The text is cut at max_chars; the result says where to continue (offset). Each call counts as one render against the account's plan.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic address of the page
delayNo
offsetNoWhere to continue after a cut
optionsNo
selectorNoCSS selector: only that part of the page
max_charsNoDefault 60000
wait_untilNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, yet the description adds real value: scripts execute in a real browser, output is truncated at max_chars with an offset to continue, and every call consumes one render from the account plan. That cost/quota disclosure is exactly the kind of behavior annotations cannot express. It stops short of covering auth requirements or failure modes (blocked pages, timeouts).

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?

Three tight sentences, front-loaded with what the tool does, then truncation mechanics, then cost. No filler and nothing repeated from the annotations or schema.

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 7-parameter tool with a nested options object, the core contract (real browser, JS executed, Markdown output, truncation, per-call billing) is all present, and no output schema means return-value description was worthwhile here. The gap is that the browser-control knobs (wait_until, delay, selector) and the untyped options object are never contextualized.

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?

At 57% schema coverage the description meaningfully clarifies max_chars (cut point) and offset (where to continue after a cut), which is more than the schema alone conveys about their relationship. However, delay, selector, wait_until, and the nested options object get no mention in the description and rely entirely on the schema.

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?

"Loads a public page in a real browser (scripts run) and returns its content as Markdown" names a specific verb, resource, and output medium. The Markdown output format is what separates it from page_to_pdf and screenshot_url, so an agent can route on it without opening any schema.

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?

The word "public" implicitly excludes logged-in or authenticated pages, and the Markdown framing hints at text-extraction rather than visual capture. But there is no explicit when-to-use/when-not statement and no sibling is named, so the choice against page_to_pdf, screenshot_url, or render_html is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources