Skip to main content
Glama

remove_item_from_group

Removes a specific page item from a group in an InDesign document. Provide the page, group, and item indices.

Instructions

Remove a page item from a group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIndexYesIndex of the page containing the group
groupIndexYesIndex of the group to remove the item from
itemIndexYesIndex of the item within the group to remove
Behavior2/5

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

Description lacks disclosure of behavioral traits: what happens to the removed item? Is it ungrouped but remains on the page? No mention of permissions or side effects. No annotations to compensate.

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

Conciseness4/5

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

Single sentence is concise and front-loaded, but might be overly terse. Slightly more detail could improve without losing conciseness.

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

Completeness2/5

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

For a straightforward removal tool, the description lacks context about what happens after removal (e.g., item remains on page, ungrouped). No output schema to clarify return value. Incomplete for an agent to understand full effect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 3 parameters with descriptions. Tool description adds no additional meaning, so baseline 3 applies due to 100% schema coverage.

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 the action ('Remove') and resource ('a page item from a group'), differentiating it from siblings like 'add_item_to_group' and 'delete_page_item'.

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 'delete_page_item' or 'ungroup'. The description does not specify context or exclusions.

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/zachshallbetter/indesign-mcp-server'

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