Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_layer_visibility

Show or hide a specific layer in an ArcGIS Pro map to control which datasets appear in the final map before export.

Instructions

Show or hide a named layer in a selected ArcGIS Pro map by updating lyr.visible. Use this before layout or map export to control which datasets appear in the final map. This mutates layer visibility in the saved .aprx project when save=true but does not alter the source dataset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.6.3
    • addedInput schema / $defs / SetLayerVisibilityInput / description
      Added value: +"Input contract for showing or hiding a layer in a selected map."
    • changedInput schema / $defs / SetLayerVisibilityInput / properties / aprx_path / description
      Previous value: -"Absolute .aprx path."New value: +"Absolute path to the saved ArcGIS Pro .aprx project file. The path must be inside a configured PathGuard allowed root. Tools operate on the saved project file, not a live open ArcGIS Pro session."
    • changedInput schema / $defs / SetLayerVisibilityInput / properties / layer_name / description
      Previous value: -"Layer (Contents) name."New value: +"Layer name as shown in the ArcGIS Pro Contents pane for the selected map. The layer must exist in the resolved map."
    • changedInput schema / $defs / SetLayerVisibilityInput / properties / map_name / description
      Previous value: -"Map name; None targets the first map."New value: +"Name of the map inside the .aprx project. Use None to target the first map returned by ArcGIS Pro."
    • addedInput schema / $defs / SetLayerVisibilityInput / properties / save / description
      Added value: +"When true, save the .aprx project after changing layer visibility."
    • changedInput schema / $defs / SetLayerVisibilityInput / properties / visible / description
      Previous value: -"True to show, False to hide."New value: +"True to show the layer in the map; false to hide it. This changes layer visibility in the .aprx project when save=true."
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. States mutation in .aprx when save=true and no alteration of source dataset. Missing details on errors (e.g., layer not found), permissions, or side effects. Adequate but not fully transparent.

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?

Three efficient sentences, front-loaded with action, use case, and behavioral note. No wasted words. Ideal length for quick understanding.

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 purpose, use case, behavioral impact, but omits map selection detail, required layer existence, and error conditions. Output schema exists but is not shown; description doesn't discuss return values. Acceptable but leaves gaps for an agent.

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?

Description adds minimal parameter info beyond input schema. Does not mention 'save', 'map_name', 'visible' fields or their nuances. Schema descriptions are detailed, but the tool description does not supplement or clarify. Coverage is 0% from description.

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?

Clear verb 'show or hide' and specific resource 'named layer in an ArcGIS Pro map'. Distinguishes from siblings like set_layer_symbology and remove_layer_from_map by focusing on visibility. Includes use case for layout/map export.

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

Usage Guidelines4/5

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

Explicitly says 'Use this before layout or map export' and mutates only visibility, not source data. Lacks explicit when-not-to-use but context implies alternatives (e.g., removal, symbology). Decent guidance.

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

Deploy Server

Other Tools