Skip to main content
Glama

Native Catalog

native_catalog
Read-only

Retrieve the Google Datastudio editor's catalog of configurable components, presets, property panels, and report/page settings to inspect available options without modifying reports.

Instructions

The editor's own catalog of what can be configured.

Default: every component type/preset (name, group, field cardinalities). types (e.g. ["simple-table", "kpi-metric/default"]) adds each one's complete property panel: tabs, sections, every setting's label, control, allowed values, range, binding. panels adds the report (theme/layout/settings) and page panels. full returns all (large; for regenerating docs/inventory/native-catalog.json). Types are created only on the unsaved viewer model, then it is reloaded; nothing is written.

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

Input Schema

NameRequiredDescriptionDefault
fullNo
typesNo
panelsNo
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'nothing is written' plus a specific mechanism: types are created only on the unsaved viewer model and then it is reloaded. That is real behavioral context beyond the annotation, and the 'large' warning for `full` is a useful cost signal. It stops short of describing pagination or output volume for non-`full` modes.

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?

Front-loaded with the core identity, then mode-by-mode detail in a compact telegraphic style. Dense but nearly every clause adds information; the only friction is the compressed grammar ('types ... adds', 'panels adds') which reads slightly clipped but remains unambiguous.

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?

An output schema exists, so return-value detail is not required, and the mode descriptions plus the no-write guarantee cover most of what an agent needs. The gap is `report_id`: it is undocumented and its relationship to `panels` is unclear, which matters for a four-parameter introspection tool whose main risk is calling the wrong mode.

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 0%, so the description carries the burden and does explain three of four parameters well, including a concrete example format for `types` (["simple-table", "kpi-metric/default"]) and an interaction note that `full` supersedes the others. But `report_id` is never mentioned at all, leaving an agent unable to tell whether it is required for `panels` or which report the panels describe.

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 states a specific resource — the editor's own catalog of configurable component types, presets, and panels — and enumerates what each mode returns. The verb is implicit (it reads/returns a catalog) rather than written, but the scope is concrete enough that an agent can distinguish it from component-manipulation siblings like components_create or components_patch.

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?

It gives useful mode-selection guidance: default for the type inventory, `types` for property panels, `panels` for report/page panels, `full` for regenerating docs and inventory files. However, it never says when to prefer this tool over inspecting live components, gives no exclusions, and `full` is only cautioned as 'large' without a size or performance framing.

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