ArcGIS Pro MCP

Overview Schema Source Related Servers Discussions Admin

create_layout

Create a new ArcGIS Pro layout page with a map frame that fills the page by default. Set page size, units, and margin to prepare maps for printing or export.

Instructions

Create a new layout page, by default with a map frame filling it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Layout name.
`margin`	No	Margin around the map frame, in page units.
`map_name`	No	Map to act on; defaults to the active map.
`page_units`	No	INCH, CENTIMETER, MILLIMETER or POINT.	INCH
`page_width`	No	Page width.
`page_height`	No	Page height.
`add_map_frame`	No	Add a map frame filling the page.
`map_frame_name`	No	Name for the map frame.	Map Frame

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.1Sep 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only mentions the default map frame, which is already captured by the schema defaults, and omits whether this is a persistent creation, requires an open project, or affects the active map.

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?

A single sentence front-loaded with the verb and resource, with zero waste. It is appropriately sized for a tool whose parameters are fully described elsewhere.

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?

An output schema exists and the input schema fully documents parameters, reducing the description's burden. However, with no annotations, the description should provide more behavioral context (e.g., prerequisites, side effects) for a creation tool; the one-sentence description leaves that gap.

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 coverage is 100%, so all 8 parameters are documented in the schema. The description adds no parameter-specific meaning beyond the default map frame behavior already encoded in the schema defaults, making the baseline 3 appropriate.

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?

States a specific verb 'Create' and resource 'layout page', and notes the default map frame. It does not explicitly distinguish itself from sibling layout tools like add_map_frame or create_map, but the resource type is clear.

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 when-to-use, prerequisites, or alternatives are mentioned. Sibling tools such as list_layouts or preview_layout exist but are not referenced, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server