Skip to main content
Glama

Report Links

report_links
Read-only

Get a Data Studio report's view, edit, and embed URLs plus a canvas-sized iframe snippet, and check whether embedding is enabled. Read-only for sharing.

Instructions

Share > Get report link / Embed report: view, edit and embed URLs plus an iframe snippet sized to the canvas; embeddable says whether embedding is enabled (settings_set on the report to change it). Read-only.

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

Input Schema

NameRequiredDescriptionDefault
page_idNo
report_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already covers the safety profile, so restating 'Read-only' adds nothing. The description does add real content beyond annotations: the three URL variants, an iframe snippet sized to the canvas, and an `embeddable` flag that signals embedding may be disabled. It stops short of saying what happens if embedding is off (error vs partial result).

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 dense sentence with the key output (links + iframe) front-loaded, followed by the embeddable caveat and the read-only note. Backticked field names aid scanning; nothing is padding.

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 no output schema, the description does useful work describing return content (view/edit/embed URLs, iframe snippet, embeddable boolean). But for a two-parameter tool with zero schema documentation, leaving both parameters unexplained is a meaningful incomplete area.

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% for both page_id and report_id, so the description carries the full burden, yet neither parameter is mentioned. It never says whether report_id is required in practice, what page_id scopes (does it change which links or iframe are produced), or how they interact.

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 concrete verb+resource: it returns view, edit and embed URLs plus a canvas-sized iframe snippet for a report, and names the UI location ('Share > Get report link / Embed report'). It does not explicitly distinguish itself from nearby siblings like report_open or report_publish, which keeps it below a 5.

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?

Implied usage is to fetch shareable links, and it routes the agent to settings_set when the `embeddable` flag needs changing. There is no explicit when-to-use/when-not guidance versus report_publish, report_publishing or report_open, so the agent must infer the boundary.

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