Skip to main content
Glama

pbi_set_visual_format_property

Set or reset formatting properties on Power BI visual objects (title, dataPoint, labels). Specify property values with type hints for accurate encoding, or reset properties to revert to default.

Instructions

Set / reset formatting properties on a visual's singleVisual.objects[<object_name>][0].properties.

Parameters

extract_folder, page, visual_id, object_name: Identify the target. object_name is the Power BI object key ('title', 'dataPoint', 'labels', 'background', 'general', etc.). properties: {property_name: value} to set. Values are encoded as Power BI literals via the type hint in property_types. property_types: {property_name: type_hint}. Valid hints:

- ``auto`` (default) — infer from Python type
- ``bool`` — booleans
- ``int`` — integers (alias: ``integer``)
- ``decimal`` — floats / numerics (alias: ``float``, ``number``)
- ``text`` — strings (alias: ``string``)
- ``color`` — hex strings ``"#RRGGBB"`` (alias: ``fill``, ``hex``,
  ``rgb``); a previously-encoded ``{"solid": {"color": ...}}``
  object is also accepted and unwrapped automatically
- ``raw`` — pass the value untouched (advanced)

Type names are case-insensitive. Unknown hints raise with the
full list.

reset_properties: Optional list of property names to delete from the visual's property bag. Use this to revert a property to Power BI's default — passing an empty string would leave the key set to a blank value instead.

Examples

Set a title (text):

pbi_set_visual_format_property(
    extract_folder, page, visual_id,
    object_name="title",
    properties={"text": "Sales", "show": True},
    property_types={"text": "text", "show": "bool"},
)

Set a fill color (single-series default):

pbi_set_visual_format_property(
    ...,
    object_name="dataPoint",
    properties={"defaultColor": "#4472C4"},
    property_types={"defaultColor": "color"},
)

Reset a property to Power BI's default:

pbi_set_visual_format_property(
    ...,
    object_name="title",
    reset_properties=["text"],
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
visual_idYes
propertiesNo
object_nameYes
extract_folderYes
property_typesNo
reset_propertiesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses the main behaviors: setting via property_types encoding, resetting by deleting properties, and handling of color types. With no annotations, this is fairly transparent, though side effects or permission requirements are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections but is verbose, especially the type hints list. While informative, it could be more concise while retaining essential details.

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

Completeness4/5

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

Given the complexity and lack of schema descriptions, the description is largely complete. It covers setting, resetting, type encoding, and provides examples. It does not discuss return values (output schema exists) or error cases beyond unknown type hints.

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?

The description documents all 7 parameters, including valid type hints for property_types and examples. This compensates for 0% schema coverage. However, extract_folder is only briefly mentioned as part of target identification without further detail.

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 it sets/resets formatting properties on a visual's object properties, with a specific verb and resource. It distinguishes from sibling tools like pbi_set_format by targeting specific visual objects via object_name.

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?

No explicit when-to-use or when-not-to-use guidance is provided. Usage is implied through examples, but alternatives or exclusions are not mentioned. This is a gap for a tool with many siblings.

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