Skip to main content
Glama

agent_convert

Convert a URL through the user's signed-in Chrome when pages sit behind login walls or return empty shells, such as Reddit, X, paywalled articles, and dashboards.

Instructions

Convert one URL through the user's own signed-in Chrome, reading the page exactly as they see it. USE THIS when convert_url hits a login wall or returns an empty shell — Reddit, X, paywalled articles, internal wikis, dashboards. Runs silently in the background over a local connection; it does not open or steal focus from any tab. Requires Chrome running with the Web2MD extension and the native host installed (npx -p web2md-mcp-server web2md-mcp-setup). For several URLs at once use agent_batch_convert; if the native host is not installed use bridge_convert_url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to convert
skillNoSkill name or id to apply — its body is returned alongside the markdown for you to follow

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / skill
      Added value: +{
      +  "description": "Skill name or id to apply — its body is returned alongside the markdown for you to follow",
      +  "type": "string"
      +}
  2. First observedv0.8.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it explains that the conversion runs silently in the background over a local connection and does not open or steal focus from any tab. It also states the prerequisite environment, Chrome running with the Web2MD extension and the native host installed, and includes the setup command.

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 front-loaded with the core purpose, then usage conditions, behavioral traits, prerequisites, and alternatives in a compact sequence. Every sentence earns its place, and the setup command is useful rather than filler.

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 annotations and no output schema, the description is nearly complete: it covers purpose, prerequisites, side effects, and sibling-tool routing. The main remaining gap is that it does not explicitly describe the return value, though the skill parameter schema implies markdown output.

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 the schema already documents both the url and skill parameters. The description adds only the scope of one URL at a time and does not elaborate on what the skill parameter does beyond what the schema provides, making the baseline score 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 states a specific verb and resource: convert one URL through the user's signed-in Chrome, reading the page as they see it. It also distinguishes this from convert_url by targeting pages behind login walls or empty shells, so an agent can select it without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: use this when convert_url hits a login wall or returns an empty shell, with concrete examples such as Reddit, X, paywalled articles, internal wikis, and dashboards. It also names alternatives for different situations: agent_batch_convert for several URLs and bridge_convert_url when the native host is not installed.

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