Skip to main content
Glama
@pokutuna/mcp-chrome-tabs

@pokutuna/mcp-chrome-tabs

by pokutuna

Read Tab Content

read_tab_content

Extract readable content from a browser tab by providing its ID from list_tabs, or omit the ID to read the active tab.

Instructions

Get readable content from a tab in the user's browser. Provide ID (from list_tabs output) to read a specific tab, or omit for the active tab.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_tab_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoTab reference from list_tabs output (e.g: ID:12345:67890). If omitted, uses the currently active tab.
startIndexNoStarting character position for content extraction (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.7.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Get readable content" usefully signals a read-only, text-extraction operation rather than a raw DOM dump, but it says nothing about truncation limits, extraction failures on restricted pages, or side effects — gaps that matter for a browser-reading tool.

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?

Two tight sentences; the core action is front-loaded and the parameter hint follows without filler. Nothing is repeated or wasted.

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

Completeness3/5

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

With only two optional parameters and no annotations this is a low-complexity tool, but there is no output schema, so the description should hint at the shape of the returned content (plain text, truncation, empty results). One phrase of return-format detail would close the remaining gap.

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 both parameters are already documented in the schema, including the ID format and the startIndex default. The description restates the id behavior and ignores startIndex entirely, adding essentially no meaning beyond the schema — the baseline 3 applies.

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?

States a specific verb and resource: "Get readable content from a tab in the user's browser." The mention of list_tabs output as the ID source implicitly separates it from list_tabs and open_in_new_tab, though it never explicitly rules out the write-oriented sibling.

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?

Gives conditional usage for the id parameter ("Provide ID ... or omit for the active tab"), which tells the agent how to pick the target. It offers no guidance on when to prefer this over open_in_new_tab or list_tabs, and no preconditions such as which pages are readable.

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