Skip to main content
Glama

browser_set_headers

Read-onlyIdempotent

Set extra HTTP headers sent with every request of THIS tab (e.g. {'X-Requested-With': 'XMLHttpRequest'}). Replaces the previous set; an empty object clears it. Does not touch the identity's own browser headers.

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": {
      "page_id": "<page_id>",
      "headers": "<headers>"
    },
    "name": "browser_set_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
headersYes
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior2/5

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

The description is candid about mutation semantics — 'Replaces the previous set; an empty object clears it' and 'Does not touch the identity's own browser headers' — which is real behavioral disclosure beyond the schema. However, it describes a state-changing operation on the tab while the annotations declare readOnlyHint=true, so the two sources conflict; the honest fix is to treat the annotation as stale, not to credit it as consistent.

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?

Three short sentences, front-loaded with the action and target, then scope and lifecycle, then the identity caveat. Nothing is redundant and the example is embedded rather than explained at length.

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

Completeness4/5

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

Covers what is set, on what scope, replacement behaviour, clearing, and the identity-boundary caveat — enough to invoke correctly with no output schema to explain. Minor gaps: whether headers survive navigation/reload, and whether they apply to subresources, are unstated.

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 only 33% — `headers` and `page_id` are undocumented objects/strings in the schema. The description compensates well for `headers` by giving a sample shape and the replace/clear semantics (which the schema cannot express), and 'THIS tab' implies what `page_id` addresses; only `in_workspace` relies on schema text.

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

Purpose5/5

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

States a specific verb, resource and scope: 'Set extra HTTP headers sent with every request of THIS tab'. The closing sentence ('Does not touch the identity's own browser headers') separates it from the identity-level browser tools in the sibling list, so an agent can pick it without opening any schema.

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?

Provides mechanics (applies to every request, replaces the previous set, empty object clears it) and a concrete example, which implies when to reach for it. It never states when NOT to use it or names an alternative such as the identity-level header path, so routing guidance is left to inference.

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.