Skip to main content
Glama

apply_style_to_range

Apply a specified style to multiple paragraphs using their unique paragraph IDs. Format targeted paragraphs with a single function call.

Instructions

Apply a style to a list of paragraphs by their paraIds.

Args: para_ids: List of paragraph paraIds to update. style_name_or_id: Style name or styleId to apply.

Returns: {"applied": int, "style_id": str, "para_ids": list[str]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
para_idsYes
style_name_or_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description must convey behavioral traits. It only states 'Apply a style' implying modification, but does not discuss destructiveness, reversibility, authentication, or handling of invalid inputs.

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?

Two sentences: first for purpose, second for parameters and return. Front-loaded, no wasted words.

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 basic inputs and outputs, but lacks details on error behavior, whether style must exist, or impact on existing formatting. Adequate for simple tool but not fully complete.

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 description compensates by explaining both parameters: 'para_ids: List of paragraph paraIds to update' and 'style_name_or_id: Style name or styleId to apply'. This adds meaning beyond basic types.

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 'apply' and the resource 'style to a list of paragraphs by their paraIds'. It distinguishes from siblings like 'create_style' or 'copy_style' by specifying it applies an existing style to multiple paragraphs.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as 'set_formatting' or 'update_paragraph'. No prerequisites or context for deciding.

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/SecurityRonin/docx-mcp'

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