Prepare your content for use with MCP
Preparing your ArcGIS Enterprise content helps AI applications find relevant resources and understand how to use them. This includes choosing appropriate content, making it discoverable through the Search Portal Content tool, and providing accurate information about its purpose and limitations.
Item owners and administrators should review the content intended for AI-assisted workflows before making it discoverable.
Select content for your workflows
Start with the questions and tasks that you want AI applications to support. Identify the maps, layers, tables, imagery, and services that those workflows need.
For example, a workflow for finding public facilities may need a facility layer that contains names, facility types, addresses, and locations. A workflow for comparing population across areas may need boundary data and population figures for a specific year.
When you select content, consider the following:
Relevance—Does the content support the intended questions or tasks?
Timeliness—Is the data up to date enough for its intended use?
Quality—Are its coverage, completeness, and limitations understood?
Ownership—Is someone responsible for maintaining it?
Access—Can the intended users access the required items and underlying services?
When several items contain similar information, make their purposes clear. For example, state whether an item contains current operational data, historical records, or a generalized dataset intended for visualization.
Make items discoverable
The Search Portal Content tool returns only items that are tagged with mcp. The tag is not case-sensitive.
To add the tag, complete the following steps:
Sign in to your portal as the item owner or as an administrator with permission to update the item.
Open the item page.
Edit the Tags field.
Add
mcpalongside the existing descriptive tags.Save your changes.
Important:
The mcp tag controls discovery through Search Portal Content, not authorization. Tools can still access an untagged item when they are given its item ID or layer URL, subject to permissions. Removing the tag does not revoke access.
Search Portal Content does not return ArcGIS Living Atlas of the World content, even if that content is available in your portal.
Provide useful item information
Item information helps people and AI applications decide whether a resource is suitable for a task. Review the title, snippet, description, tags, and terms of use.
For instructions on editing these details, see Configure item details and settings.
Use a descriptive title
Choose a title that distinguishes the item from similar resources. Include the subject and geographic area, and add a time period when it is relevant.
For example:
| Less informative title | More informative title |
|---|---|
| Facilities_Final | Redlands Public Facilities |
| Population_Data | County Population Estimates – 2025 |
| Roads_Copy2 | County Road Closures – Current Conditions |
Avoid internal abbreviations or file names that agents or people outside of your organization may not understand.
Write a concise snippet
Use the snippet, shown as the summary on the item page, to explain what the item contains and its main purpose. People and AI applications should be able to judge its relevance without opening every layer or table.
For example:
Locations and attributes of public libraries, parks, and community centers in Redlands, California, for facility lookup and neighborhood planning.
Explain the content and its limitations
Organize the description so that readers can answer practical questions about the data.
| Information | What to explain |
|---|---|
| Purpose | Why the resource exists and which tasks it supports. |
| Contents | The layers or tables included and what each represents. |
| Important attributes | Fields needed to interpret, filter, or summarize the data. |
| Geographic coverage | The area represented and any significant gaps. |
| Time coverage | When observations were collected, or the period they describe. |
| Units and definitions | Measurement units, coded values, abbreviations, and specialized terms. |
| Maintenance | The responsible organization and expected update frequency. |
| Limitations | Known omissions, uncertainty, or uses for which the data is not suitable. |
Document only facts that you can verify. Avoid describing an item as current, complete, or authoritative unless you have established what those terms mean for that resource.
For example, distinguish a facility's published opening hours from its live operational status. A dataset of opening hours does not tell you whether a facility is open during an emergency.
Add descriptive tags
Keep tags relevant to the content. Use terms that people are likely to recognize, including the subject, location, and common terminology.
For a public facilities layer, descriptive tags might include public facilities, libraries, parks, community centers, and Redlands, alongside the required mcp tag.
Document use conditions
Include attribution requirements, usage restrictions, and other conditions in the item's terms of use.
Note:
Written restrictions provide context but do not enforce access. Configure sharing and permissions separately.
Example item information
The following fictional example shows the level of detail to provide. Replace it with verified details for your own content.
Title
Redlands Public Facilities
Snippet
Locations of public libraries, parks, and community centers in Redlands, California, for facility lookup and neighborhood planning.
Description
This feature layer contains point locations for public facilities in Redlands. Each record represents a facility and includes its name, facility type, street address, and published opening hours.
The FacilityType field identifies libraries, parks, and community centers. The OpeningHours field contains published schedules and does not indicate live operational status. Missing opening hours mean that schedule information is unavailable.
The layer supports questions such as "Which community centers are in Redlands?" and "What is the address of this library?"
Facility locations are intended for general planning and reference. They do not identify building entrances or accessible routes. Review the recorded update date before you use the information for time-sensitive decisions.
Tags
mcp, Redlands, public facilities, libraries, parks, community centers
Review layers and attributes
Item descriptions provide an overview, but layer definitions and attribute values should also be easy to understand.
As you prepare content, do the following:
Use meaningful layer names and field aliases.
Explain coded values and abbreviations.
Identify units for measurements such as distance, area, or elevation.
Clarify the meaning of dates and timestamps.
Explain whether missing values mean unknown, not applicable, or not collected.
Check that descriptions stay consistent with the published schema.
For example, a field named STATUS is difficult to interpret unless its values are defined. Explain whether a value represents a planned facility, an active facility, or a permanently closed facility.
Caution:
Do not rename fields without assessing the effect on existing applications. Improve field aliases and documentation instead, where appropriate.
Verify discovery and use
Test with the user identity or credential intended for the workflow.
Connect an MCP client to the catalog.
Ask for the prepared content using a realistic request, such as Find public facility data for Redlands.
Inspect the tool activity and results to confirm that the intended item was found.
Ask the application to describe the relevant layer. The application typically uses Describe Layer.
Run a simple query, such as with Query Data, and compare the response with the underlying records.
Evaluate whether the application selected the correct resource, interpreted its attributes appropriately, and respected the documented limitations.
If the results are unexpected, check the mcp tag, permissions, search terms, item information, and service availability. Clear descriptions improve context, but they do not guarantee that an AI application will interpret every request correctly.
Maintain prepared content
Review item information when data, schemas, coverage, or service URLs change. Update descriptions when a dataset is replaced or its intended use changes.
Retest representative requests after significant updates. Make this preparation part of routine content maintenance so that the information available to AI applications stays consistent with the underlying GIS resources.
Next steps
For the available tools, see Default MCP catalog overview.
To expose a web tool as a custom MCP tool, see Expose a web tool as a custom MCP tool.