Skip to main content
Glama

set_textbox_style

Set styling on a named textbox in a paginated report. Adjust font, color, borders, alignment, padding, and more with optional parameters.

Instructions

Set styling on a named Textbox. Properties route to the right nested Style node automatically: background_color, border_*, vertical_align, padding_*, writing_mode go on Textbox/Style; text_align on Paragraph/Style; font_*, color, format on TextRun/Style; can_grow / can_shrink go DIRECTLY on Textbox (not inside Style). All fields optional — only what's passed gets written. Cell-level styling: every tablix cell is a Textbox with a unique name, so use this tool with the cell's textbox name (e.g. 'HeaderAmount').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
colorNoText color — '#RRGGBB' or named.
formatNoNumber/date format (e.g. '#,0.00', 'C2', 'd').
can_growNoAllow textbox to grow vertically when content exceeds the height. Direct Textbox child, not Style.
font_sizeNoRDL size, e.g. '11pt'.
can_shrinkNoAllow textbox to shrink when content is shorter than the height. Direct Textbox child, not Style.
text_alignNoLeft | Center | Right | Justify | General.
font_familyNo
font_weightNoNormal | Bold | Lighter | ... or numeric.
padding_topNoRDL size (e.g. '2pt', '0.05in').
border_colorNo
border_styleNoNone | Solid | Dotted | Dashed | Double.
border_widthNo
padding_leftNo
textbox_nameYes
writing_modeNoHorizontal | Vertical | Rotate270 — text orientation. Useful for narrow column headers.
padding_rightNo
padding_bottomNo
vertical_alignNoTop | Middle | Bottom.
background_colorNo
Behavior4/5

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

With no annotations, description carries full burden. It discloses that properties route to different style nodes and that can_grow/can_shrink go directly on Textbox. States all fields optional. Missing details on permissions or side effects, but adequate for a styling tool.

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?

Efficient, well-structured paragraph. Front-loaded with main action, followed by routing details, optionality, and usage example. No waste.

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 20 parameters, 2 required, and no output schema, the description covers routing and usage context well. Lacks mention of return value, but as a setter, that's less critical. Adequate for the tool's complexity.

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 55%, but description adds valuable info on property routing ('background_color goes on Textbox/Style', etc.) and clarifies textbox naming for tablix cells. Supplements schema definitions meaningfully.

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?

Description clearly states 'Set styling on a named Textbox' with specific verb and resource. It details property routing to nested style nodes, distinguishing it from siblings like set_textbox_value or set_textbox_action.

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?

Provides clear context: cell-level styling using unique textbox names, and emphasizes that only passed fields are written. However, lacks explicit guidance on when not to use this tool versus alternatives like set_textbox_style_bulk.

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