Skip to main content
Glama

duplicate_master_spread

Duplicate a master spread by name, assign a new name, and control its placement within the document.

Instructions

Duplicate a master spread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesMaster spread name to duplicate
newNameYesName for the duplicated master spread
positionNoAT_END
Behavior1/5

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

Lacking any behavioral disclosure—no mention of side effects, whether the operation is destructive, or what output is returned. With no annotations, the description fails to inform the agent about key behavioral traits.

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

Conciseness2/5

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

Extremely short (one sentence) but omits important context for a tool with multiple parameters. Under-specification reduces effectiveness despite brevity.

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?

Given the moderate complexity (3 parameters, no output schema), the description lacks complete context such as what happens to the original spread, whether duplicates are linked, or how position affects placement. Insufficient for an agent to fully understand the tool's behavior.

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 2 of 3 parameters (name, newName) with descriptions, and position has an enum. The description adds no extra parameter information beyond the schema, so baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Duplicate a master spread', specifying the verb and resource. It is specific enough to convey the action, though it does not distinguish from sibling duplicate tools like duplicate_page or duplicate_spread.

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 create_master_spread or duplicate_spread. No prerequisites or context provided.

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