Skip to main content
Glama

pbi_add_visual

Add any visual to a Power BI report page — the single entry point for visual creation. Supports charts, tables, cards, slicers, maps, and more with configurable fields.

Instructions

Add any visual to a report page — the single entry point for visual creation.

visual_type: card, labelled_card, multi_row_card, bar_chart, stacked_bar_chart, stacked_column_chart, clustered_column_chart, hundred_percent_stacked_bar_chart, hundred_percent_stacked_column_chart, ribbon_chart, line_chart, area_chart, stacked_area_chart, hundred_percent_stacked_area_chart, donut, pie_chart, treemap, funnel, table, waterfall, scatter_chart, combo_chart, slicer, gauge, kpi, matrix, map, text_box. config: per-type keys — categorical charts: category_column + value_measure (+ legend_column); axis charts: axis_column + value_measures (list); card/gauge: measure; table: columns (list); matrix: rows + values (lists); scatter: category_column + x_measure + y_measure; combo: category_column + bar_measures + line_measures; kpi: indicator_measure + trend_column; slicer: column (+ slicer_type); map: location (+ measure); text_box: text. Error messages name any missing key. Prefer pbi_add_visual_from_intent when you have a business intent rather than an exact type. dry_run: when True, run all validation and binding logic but skip the layout disk write — response carries dry_run=True and a write_log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes
pageYes
titleNo
widthNo
configNo
heightNo
dry_runNo
visual_typeYes
extract_folderYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full responsibility. It explains dry_run behavior and error messages, but doesn't disclose potential side effects like overwriting existing visuals or permission requirements.

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 well-structured: purpose statement, parameter explanations, usage guidance, and alternative mention. Every sentence adds value without redundancy.

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?

The description omits key required parameters: x, y, page, extract_folder. While visual_type and config are well covered, five required parameters are not explained, leaving significant gaps for correct invocation.

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?

Although schema coverage is 0%, the description adds significant value by detailing visual_type options and config keys per type. It also explains dry_run behavior beyond the schema's boolean type.

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 tool adds any visual to a report page, positions it as the single entry point for visual creation, and distinguishes it from the sibling pbi_add_visual_from_intent.

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?

Explicitly advises using pbi_add_visual_from_intent for business intents, and describes dry_run for validation without committing changes. Provides clear context on when to use this tool versus alternatives.

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/imnotStealthy/powerbi-mcp-local'

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