Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

print_to_pdf

Generate a PDF from the current browser page, with optional tab selection, landscape orientation, and background graphics.

Instructions

Generate a PDF of the current page

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": "print_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
landscapeNoLandscape orientation
printBackgroundNoPrint background graphics (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/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 and largely drops it: it does not say whether the PDF is returned inline, written to disk, or downloaded, nor whether rendering waits for the page to settle. The only behavioral hint (default true for backgrounds) lives in the schema, not the description.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is efficient rather than padded, though it verges on under-specification for a tool with no annotations.

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 no annotations and no output schema, the definition should at minimum explain what the agent receives back and whether the operation is a safe read. Neither is covered, leaving a real gap for a tool whose output destination is the main unknown.

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 all three parameters (tabId, landscape, printBackground) are already documented in structured data; baseline 3 applies. The description adds nothing beyond that and does not clarify how tabId interacts with the stated "current page" scope.

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 gives a specific verb and resource ("Generate a PDF") plus a scope ("the current page"), which is unambiguous on its own. It does not distinguish itself from the nearest sibling, take_screenshot, nor explain the tension between "current page" and the optional tabId parameter.

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 guidance on when to choose PDF generation over take_screenshot or take_snapshot, and no stated preconditions. The agent must infer usage entirely from the tool name and the single sentence.

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