Skip to main content
Glama
Mehmoodqureshi

chrome-mcp

by Mehmoodqureshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_as_markdown

Extract clean markdown from a Chrome tab or frame, turning web pages into readable text for processing.

Instructions

Read the page (or subtree) as readable markdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoTab id (default: active tab)
frameIdNoFrame id from frames_list
maxBytesNoCap returned content at N UTF-8 bytes (default 262144); the full payload still lands in results/
selectorNo
allFramesNoAct on the first match in ANY frame (the element may be in an iframe)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.5
    • changedInput schema / properties / allFrames / description
      Previous value: -"Search every frame of the tab and act on the first that matches - use when a selector should match but does not (the element is in an iframe)"New value: +"Act on the first match in ANY frame (the element may be in an iframe)"
    • changedInput schema / properties / frameId / description
      Previous value: -"Act inside this frame (ids come from frames_list)"New value: +"Frame id from frames_list"
    • changedInput schema / properties / maxBytes / description
      Previous value: -"Cap the returned content at this many UTF-8 bytes (default 262144). A truncated result reports truncated/totalBytes/returnedBytes. The full payload is still written to the task's results/ dir."New value: +"Cap returned content at N UTF-8 bytes (default 262144); the full payload still lands in results/"
    • changedInput schema / properties / tabId / description
      Previous value: -"Target tab id (defaults to the active tab)"New value: +"Tab id (default: active tab)"
  2. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / allFrames
      Added value: +{
+  "description": "Search every frame of the tab and act on the first that matches - use when a selector should match but does not (the element is in an iframe)",
+  "type": "boolean"
+}
    • addedInput schema / properties / frameId
      Added value: +{
+  "description": "Act inside this frame (ids come from frames_list)",
+  "type": "number"
+}
    • addedInput schema / properties / maxBytes
      Added value: +{
+  "description": "Cap the returned content at this many UTF-8 bytes (default 262144). A truncated result reports truncated/totalBytes/returnedBytes. The full payload is still written to the task's results/ dir.",
+  "type": "number"
+}
  3. First observedv0.6.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations present, the description must carry behavioral disclosure, but it only states that the action is a read and the output is markdown. It does not describe side effects, persistence, auth requirements, failure modes, or frame-related behavior. The maxBytes parameter description mentions results/, but the tool description itself does not explain that behavior.

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 short sentence with the core action and output format front-loaded. There is no filler or redundant context.

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

Completeness2/5

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

The tool has five parameters, no annotations, and no output schema, yet the description offers only a high-level capability. It does not explain the return value, what 'subtree' means for selector, how maxBytes affects results, or when to choose this over siblings. An agent would need to inspect the schema and infer execution semantics on its own.

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 80%, so the schema already documents tabId, frameId, maxBytes, and allFrames; the high-coverage baseline applies. The description adds no parameter-level detail and does not clarify the undocumented 'selector' parameter, so it neither improves nor harms parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Read'), a resource ('the page (or subtree)'), and an output format ('readable markdown'), so an agent can tell this is a content-extraction tool. It does not explicitly compare with get_text/get_html/snapshot, but the markdown format is distinct enough to differentiate from siblings.

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?

The description contains no when-to-use language, prerequisites, or alternatives. It does not say 'use this instead of get_text/get_html when you want markdown,' and it offers no exclusions. An agent must infer use cases solely from the tool name and sibling list.

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