Skip to main content
Glama

find_textboxes_by_style

Search textboxes in Power BI paginated reports using style filters (background color, font, alignment, etc.). Returns matched textbox names and locations for efficient bulk styling.

Instructions

Search for textboxes matching one or more style filters. Filters AND together (every supplied filter must match). Returns [{name, location, matched_fields}] where location is best-effort 'body' / 'header' / 'footer' / 'tablix:' / 'rectangle:'. Returns [] when no filters supplied. Pair with set_textbox_style_bulk for discovery+apply patterns (e.g. 'recolor every red textbox').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
colorNo
formatNo
font_sizeNo
font_styleNo
text_alignNo
font_familyNo
font_weightNo
padding_topNo
border_colorNo
border_styleNo
border_widthNo
padding_leftNo
writing_modeNo
padding_rightNo
padding_bottomNo
vertical_alignNo
text_decorationNo
background_colorNo
Behavior4/5

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

Describes return format with name, location, matched_fields and location best-effort places. States returns [] when no filters supplied. No contradictions. With no annotations, description carries full burden and does well.

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?

Three concise sentences with front-loaded purpose, logic, return format, and pairing suggestion. No redundant information.

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?

Covers return format and empty case, but given 19 parameters and no output schema, lacks details on value formats, case sensitivity, or exact match semantics. Adequate but could use examples.

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%. Description only mentions 'style filters' but does not explain any parameter values or formats. Parameter names are somewhat self-explanatory, but lack of examples or accepted values hurts usability.

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?

Clear verb 'Search for' and resource 'textboxes' with 'style filters'. Distinguishes from sibling find_textbox_by_value by focusing on style rather than value. The AND logic is explicitly stated.

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

Usage Guidelines4/5

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

Explicitly mentions AND filtering and pair with set_textbox_style_bulk for discovery+apply patterns. Provides example. Does not explicitly state when not to use, but context implies alternative sibling tool for value search.

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/mafaq229/pbirb-mcp'

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