Skip to main content
Glama
Mehmoodqureshi

MCP Browser Extension

by Mehmoodqureshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_as_markdown

Extract a Chrome page or selected subtree as readable Markdown for MCP agents to analyze or summarize.

Instructions

Read the page (or subtree) as readable markdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoTab id (default: agent's 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. Changed1 schema field changedv0.9.24
    • changedInput schema / properties / tabId / description
      Previous value: -"Tab id (default: active tab)"New value: +"Tab id (default: agent's tab)"
  2. 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)"
  3. 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"
+}
  4. First observedv0.6.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about authentication requirements, side effects, dynamic content handling, rate limits, or how the 'readable markdown' is produced; only the output format is mentioned.

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, front-loaded sentence with no filler. Every word contributes to stating the action, target, and output format.

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?

Given five parameters, no annotations, and no output schema, the description is too thin. It omits usage context, behavioral traits, and any explanation of how maxBytes, frame targeting, or allFrames affect the result.

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%, which meets the high-coverage baseline. The description adds only a hint about subtree scope via '(or subtree)', which loosely relates to the undocumented selector parameter, but it otherwise does not clarify any parameter semantics beyond the schema.

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 states a clear verb ('Read') and resource ('page (or subtree)') plus the output format ('readable markdown'). It distinguishes from siblings like get_text and get_html by naming markdown, but it does not explicitly contrast itself with those alternatives.

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?

There is no when-to-use guidance, no exclusions, and no named alternatives. An agent can infer that this tool is for reading page content as markdown, but the description does not say when to choose it over get_text, get_html, or snapshot.

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