Skip to main content
Glama

Report Pdf

report_pdf
Read-only

Render a Google Data Studio report or selected pages to PDF using Google's PDF service and save it to a local file path.

Instructions

File > Download as > PDF: render the report (all pages in navigation order, or page_ids) with Google's PDF service and save it to a local .pdf path.

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": {
      "path": "<path>"
    },
    "name": "report_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
page_idsNo
report_idNo
page_numbersNo
expand_tablesNo
add_report_linkNo
print_backgroundNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description earns credit for disclosing the two behaviors that matter: rendering goes through "Google's PDF service" and the output is written to a local .pdf path (a real filesystem side effect not implied by readOnlyHint). It still omits failure modes, size/latency limits for large reports, and whether an existing file at path is overwritten.

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 compact sentence that front-loads the user-facing action and then the mechanics. Every clause carries information; the only soft cost is the menu-path prefix, which is still useful orientation.

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?

An output schema exists, so return values need no explanation, but the tool has seven options including four non-obvious booleans (expand_tables, print_background, add_report_link, page_numbers) that an agent cannot set correctly from this definition. For an export tool with that many switches, the description leaves the majority of call-shaping decisions undocumented.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description must carry the burden and it does not. It only explains page_ids and the default all-pages-in-navigation-order behavior; report_id, page_numbers, expand_tables, add_report_link, and print_background are left entirely undefined, and the required path parameter is only obliquely referenced.

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?

"render the report ... and save it to a local .pdf path" gives a specific verb (render/export) and resource (report PDF), plus the UI analogue "File > Download as > PDF" that pins down intent. It does not explicitly contrast with other report_* tools, but the export-to-file framing is distinct enough from siblings like report_content_get or report_publish.

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 implies when to use it (you want a downloadable PDF artifact rather than structured data), and the "File > Download as > PDF" mapping reinforces that. There is no explicit when-not guidance, no mention of alternatives for getting report content in another format, and no prerequisites stated.

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