Describe Item
The describe_item tool returns detailed information about a single organization item, given its item ID. AI agents typically call it after Search Portal Content has narrowed the candidates down to one—or whenever a user pastes an item ID directly into a prompt and expects a description back.
Tool name
describe_item
Tool alias
Describe Item
Objective
Retrieve detailed information about a specific organization item by its item ID, optionally including the service definition for service items or the item data for non-service items.
Usage guidance
describe_item retrieves information about an item in the organization by its item ID. The client can also request additional details about the item by using the fetchAdditionalDetails parameter.
The fetchAdditionalDetails parameter defaults to true and should generally be left at the default—additional details are usually valuable and inexpensive to fetch.
When fetchAdditionalDetails is true, what gets returned alongside the core item information depends on the item's type:
Service items with an ArcGIS Server REST endpoint—For items such as feature services and map services, the response includes the service definition of the item. This is the service-level metadata an agent needs to plan further calls, including the list of layers and tables, spatial reference, and capabilities.
Non-service items—For items such as web maps and dashboards, the response includes the item's data JSON from its
/dataendpoint.
If the request to fetch additional details succeeds, those details are returned in the additionalDetails field. If the request fails for any reason, the tool still returns the core item information; the additionalDetails field is omitted from the response, and the error is logged. The tool does not fail the whole call.
When to use
- The client wants the full details of an organization item, such as a web map, dashboard, or service item.
When not to use
- The client needs the full details of an individual layer in a service item, typically before running a layer query.
describe_itemdoes not return per-layer definitions. Use Describe Layer instead.
Tip:
Calling describe_item first on a service item is a useful precursor to describe_layer: its service definition enumerates the available layers and their IDs, which you can then pass to describe_layer.
Sample prompts to test the tool
Send any of the prompts below to your MCP-compatible AI client to verify that describe_item is working correctly. The prompts are grouped to exercise different aspects of the tool—coverage of various item types, edge cases, multi-item comparisons, metadata-quality questions, owner and lineage queries, and capability checks.
Note:
These prompts are for illustration only. Before you use them, modify them to match the data published in your ArcGIS Enterprise environment.
Item-type coverage
Can you explain the California feature service?
Can you explain the WMS services I have in my ArcGIS Enterprise?
Describe the dem image service.
Tell me about the Landsat8 image service.
Explain the PrintingTools geoprocessing service.
Tell me about the Geometry utility service.
What is the SampleWorldCities OGCFeatureServer?
Edge cases
Describe the Vision Zero Safety service without fetching extra details.
Describe item ID
0000000000000000.
Comparison and multi-item
Compare the California and SanFrancisco feature services—do they share the same schema?
What is the difference between the dem, Landsat8, and cog image services?
Are the SampleWorldCities items (Map Service, OGCFeatureServer, and WMS) backed by the same data?
Metadata quality
Which of my hosted feature services have a completeness score below 30?
Describe New Jersey Preserved Farms—is the metadata publication-ready?
What is the access level and sharing status of the DE Development Applications service?
Owner and lineage
- Show me everything about every item created on the same day as the California feature service.
Capability checks
Can the Vision Zero Safety service be edited, or is it query-only?
What spatial reference does the DE Development Applications service use?
What export formats does New Jersey Preserved Farms support?
Does the California feature service have sync enabled?
What is the max record count on the SanFrancisco service?