Skip to main content
Glama

Read the page

well_browser_read_page
Read-only

Read the page as one line per element, role "name" [ref_N], indented by depth. filter "interactive" keeps the controls only; ref reads one element's subtree; depth limits the levels (default 15). It acts in the Well tab group of the caller's own Chrome, picked with well_select_browser (or the only one connected). Refs come from well_browser_read_page or well_browser_find and go stale when the page changes: read again then.

Input Schema

NameRequiredDescriptionDefault
refNo
depthNo
filterNo
tab_idNoThe tab, as tabs_context lists it (tab-N). Default: the active tab of the Well group.
workspace_idNoTarget workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
tabsNo
textNo
errorNo
notesNo
statusNo
successYes
state_changesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "conversation_id": {
      +      "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
      +      "type": "string"
      +    },
      +    "conversation_id_note": {
      +      "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
      +      "type": "string"
      +    },
      +    "conversation_id_source": {
      +      "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
      +      "enum": [
      +        "host_meta",
      +        "argument",
      +        "minted"
      +      ],
      +      "type": "string"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "newly_connected": {
      +      "description": "Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "service_id": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "service_id"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "notes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "state_changes": {
      +      "items": {
      +        "oneOf": [
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "tab_id": {
      +                "maxLength": 4096,
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "type": {
      +                "const": "tab_opened",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "tab_id"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "download_id": {
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "type": {
      +                "const": "download_started",
      +                "type": "string"
      +              },
      +              "url": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "download_id",
      +              "url"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "download_id": {
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "path": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              },
      +              "size_bytes": {
      +                "maximum": 9007199254740991,
      +                "minimum": 0,
      +                "type": "integer"
      +              },
      +              "type": {
      +                "const": "download_completed",
      +                "type": "string"
      +              },
      +              "url": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "download_id",
      +              "url"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "download_id": {
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "error": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              },
      +              "type": {
      +                "const": "download_failed",
      +                "type": "string"
      +              },
      +              "url": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "download_id",
      +              "url"
      +            ],
      +            "type": "object"
      +          }
      +        ]
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "enum": [
      +        "ok",
      +        "failed"
      +      ],
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    },
      +    "tabs": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "active": {
      +            "type": "boolean"
      +          },
      +          "tab_id": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "title": {
      +            "maxLength": 4096,
      +            "type": "string"
      +          },
      +          "url": {
      +            "maxLength": 4096,
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "tab_id",
      +          "title",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "text": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "success"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely non-structured behavior: scoping to the caller's own Chrome tab group, the default 15-level depth, and the crucial warning that refs are stale after page changes and must be re-read. Return format is also spelled out. It does not describe an error mode for a stale ref, which would complete the picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the output format before the parameter notes and the environment/staleness caveats. The telegraphic style ("ref reads one element's subtree") is efficient but slightly terse, and the tab-group sentence interrupts the parameter flow.

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

Completeness5/5

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

For a browser page-reading tool with seven optional parameters and an output schema, the description supplies what the structured fields cannot: the line format, depth default, tab-group targeting, and ref lifecycle. An agent can invoke it correctly and knows to re-read after mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 57%, and the description compensates for the undocumented parameters by explaining filter, ref and depth semantics, including the default depth of 15, which the schema does not state. tab_id, workspace_id and conversation_id are covered by schema descriptions, so the meaningful gaps are closed.

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 and resource ('read the page') and defines exactly what the output looks like: one line per element with role, name and ref, indented by depth. It stops short of contrasting itself with well_browser_get_page_text, which is the closest sibling an agent might confuse it with, so differentiation is only partial.

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

Usage Guidelines4/5

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

It explains the practical knobs (filter=\"interactive\" for controls only, ref for a subtree, depth default 15) and states the operational prerequisite: the tool acts in the caller's own Chrome tab group picked with well_select_browser, or the only connected one. It also gives a clear re-read rule when refs go stale. No explicit when-not guidance versus get_page_text or wait.

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