Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_get_web_content

Fetch HTML or visible text from the current browser page or a specified URL, optionally limited to one element via CSS selector.

Instructions

Get HTML and text content from the current page or a specific URL. If you want to get text content of one element without html tags , set textContent to be true.Otherwise, set htmlContent to be true to get html content. Noted, to get text content of whole page is not yet supported.

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": {
      "envId": "<envId>"
    },
    "name": "chrome_get_web_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to fetch content from. If not provided, uses the current active page
envIdYesEnvironment ID for the browser environment to operate.
selectorNoCSS selector to get content from a specific element. If provided, only content from this element will be returned
htmlContentNoGet the visible HTML content of the page. If true, textContent will be ignored (default: false)
textContentNoGet the visible text content of the page with metadata. Ignored if htmlContent is true (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one real limitation (whole-page text extraction is unsupported), but it omits whether the operation is read-only, what happens when url is omitted versus supplied, and what the response looks like. It also conflicts with the schema, which documents textContent as returning visible page text with metadata by default, while the description says whole-page text is not supported.

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

Conciseness3/5

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

The core purpose is front-loaded, which is good, but the flag discussion is a run-on with missing spaces and typographic slips ('Noted,', 'tags ,', 'be true.Otherwise') that hurt readability. The third sentence spends words on a limitation stated vaguely enough to conflict with the schema.

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?

With five parameters, one required, no annotations, and no output schema, the description should settle mode precedence, defaults, and return shape. Instead it leaves the htmlContent/textContent interaction ambiguous and directly contradicts the documented default behavior for textContent, so an agent cannot reliably predict the result of a call.

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 coverage is 100%, so the schema already documents all five parameters, making 3 the baseline. The description's added guidance on the htmlContent/textContent flags partially duplicates and partially muddies the schema, since its precedence explanation and its whole-page-text caveat disagree with the documented defaults.

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 first sentence states a specific verb and resource: retrieve HTML and text content from the current page or a given URL. It is clear what the tool returns, but it does not distinguish itself from sibling readers such as chrome_get_element_attributes or chrome_get_interactive_elements.

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?

The description gives partial mode-selection guidance: set textContent for tagless text of a single element, set htmlContent for HTML. It stops short of saying when to prefer this tool over sibling content readers, and it states no preconditions (e.g., an active browser session or envId requirement).

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