Skip to main content
Glama
HorizunGroup

Horizun PBI MCP

Official
by HorizunGroup

pbi_export_report_content

Export the data displayed in a Power BI report to Excel or PDF, replicating what clients see. Specify pages, visuals, or custom DAX queries; it runs read-only against the live model and lists any filters that could not be applied.

Instructions

Exporta el CONTENIDO del informe: los datos que muestra el tablero.

A diferencia de pbi_export_excel y pbi_generate_pdf_report, que documentan el proyecto, esto exporta lo que el cliente ve. select admite tres formas, combinables:

  • pages: ["Matriz de Riesgos"] -> la tabla que hay detras de CADA visual de esas paginas (por nombre visible o id interno).

  • visuals: ["15b0fc11e628..."] -> solo esos visuales.

  • queries: [{name, rows:["Tabla[Columna]"], values:["Medida"], filters:[{field, values, exclude?}], top_n?}] -> lo que el cliente declare, sin referirse a ningun visual.

Cada consulta se reconstruye a partir de los campos del visual, se ejecuta en SOLO LECTURA contra el modelo en vivo y sale como una hoja de Excel (format: xlsx|pdf|both).

Necesita el modelo en vivo: los datos solo existen en el motor, no en el .pbip. Con auto_open abre el informe en Desktop si hace falta, y se NIEGA a exportar si el modelo esta abierto pero sin procesar, en vez de publicar un archivo en blanco. Con dry_run devuelve el DAX que ejecutaria sin tocar el motor ni escribir nada.

Cada hoja declara con que filtros se saco y, sobre todo, cuales no se pudieron aplicar. Los visuales sin consulta tabular -textos, imagenes, formas- se listan aparte con el motivo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
formatNoxlsx
selectYes
dry_runNo
max_rowsNo
auto_openNo
file_nameNo
max_rows_pdfNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description goes far beyond the sparse annotations: it discloses that queries run 'en SOLO LECTURA,' that the tool refuses to export if the model is open but unprocessed, that dry_run returns DAX without touching the engine, and that each sheet declares applied and unapplied filters. This is rich behavioral disclosure and does not contradict the annotations.

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?

The description is dense but well-structured: one-line purpose, then clear line breaks for select forms and behavioral details. Every sentence adds value; there is no filler or repetition. It is front-loaded and appropriately sized for the tool's complexity.

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

Completeness5/5

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

For a tool with nested select objects, 8 parameters, and an output schema, the description is remarkably complete. It covers what the tool exports, how to select content, execution modes, safety guarantees, output format, and sibling differentiation. An agent can correctly invoke it without additional clarification.

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 0%, so the description bears full responsibility. It thoroughly explains the select parameter's three combinable forms, including pages, visuals, and queries with their sub-fields. It also explains format values, dry_run, and auto_open. However, it does not explicitly explain max_rows, max_rows_pdf, file_name, or title, though these are reasonably inferable from names/defaults.

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?

The description clearly states the verb and object: 'Exporta el CONTENIDO del informe: los datos que muestra el tablero.' It also explicitly contrasts with pbi_export_excel and pbi_generate_pdf_report, which 'documentan el proyecto,' making the purpose unmistakable and distinct from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternatives explicitly ('A diferencia de pbi_export_excel y pbi_generate_pdf_report') and explains what makes this tool different: it exports what the client sees. It also provides clear context for when to use it, including the live-model requirement and the dry_run/auto_open modes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HorizunGroup/horizun-pbi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server