Skip to main content
Glama

promote_list_item

Promotes a list item by decreasing its indentation level by one. Returns the paragraph ID and new indentation level. Raises an error if the paragraph is not a list item.

Instructions

Decrease the list indentation level (ilvl) of a paragraph by 1, minimum 0.

Returns {para_id, ilvl}. Raises ValueError if paragraph is not a list item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
para_idYes

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 burden. It discloses the mutation (decrease ilvl), the minimum value (0), return values ({para_id, ilvl}), and error condition (ValueError if not a list item). This is fairly transparent, though it could mention additional effects like numbering updates.

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 extremely concise: two sentences that front-load the action and immediately follow with return and error information. Every sentence adds value with no redundancy.

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 tool's low complexity, the description covers the essential aspects: action, return, and error condition. However, it could be more complete by describing how ilvl relates to list depth or by referencing sibling tools for broader context.

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?

There is one parameter, para_id, with 0% schema description coverage. The description does not explain what para_id represents beyond the schema's title 'Para Id'. It fails to provide context on how to obtain it or any format/syntax details, leaving a gap in semantic understanding.

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 action: 'Decrease the list indentation level (ilvl) of a paragraph by 1, minimum 0.' It uses a specific verb and resource, and distinguishes from the sibling tool 'demote_list_item' (which does the opposite).

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?

The description does not explicitly state when to use this tool vs alternatives like demote_list_item. It mentions a precondition (paragraph must be a list item) but lacks guidance on when promotion is appropriate or when to use other list-related tools.

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

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