Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Locations

list_project_locations
Read-onlyIdempotent

Retrieve a paginated list of project locations. Filter by IDs, parent, code, search, or depth range to find specific locations.

Instructions

Return a list of Locations associated with a Project. Use this to enumerate Project records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Project records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Core > Project. Endpoint: GET /rest/v1.0/projects/{project_id}/locations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__parent_idNoQuery string parameter — return location(s) with the specified parent_ids.
filters__codeNoQuery string parameter — return location(s) matching any of the specified codes in the search term.
filters__searchNoQuery string parameter — returns item(s) matching the specified search query string.
filters__search_with_codeNoQuery string parameter — return item(s) where the location code or the location name match the search term
filters__superlocations_forNoQuery string parameter — return superlocations (ancestors) of the specified location ids.
filters__sublocations_forNoQuery string parameter — return sublocations (descendants) of the specified location ids.
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__depth_rangeNoQuery string parameter — return item(s) with a tree depth within the specified range. Examples: `0...1` - Parents and children `0...2` - Parents, children, and grandchildren `1...2` - Children and grandchildren
Behavior1/5

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

The description incorrectly states the output as 'Project records' whereas the tool returns locations. This is a factual error that misleads the agent. Annotations correctly indicate read-only, but the description adds misleading information.

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?

The description is relatively concise but includes a major inaccuracy ('Project records') which degrades its reliability. It is not front-loaded effectively due to the error.

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 13 parameters and no output schema, the description fails to compensate adequately. It omits details on filter parameters and output structure. The error further reduces completeness.

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?

With 100% schema coverage, the description adds some value by highlighting pagination controls and required project_id, but does not explain the many filter parameters. Baseline 3 is 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?

The description clearly states the tool returns a list of locations for a project, with a specific verb and resource. However, it confusingly mentions 'enumerate Project records' instead of locations, slightly reducing clarity.

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

Usage Guidelines3/5

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

The description provides context for when to use the tool (pagination, filtering) but does not mention when not to use or any alternatives. It lacks explicit exclusions.

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/TylerIlunga/procore-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server