Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Regions

list_project_regions
Read-onlyIdempotent

Retrieve paginated project regions for a company. Use to find IDs or filter by query parameters. Requires company ID.

Instructions

Return a list of Project Regions. Use this to enumerate Company Settings when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Company Settings. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Company Admin > Company Settings. Endpoint: GET /rest/v1.0/companies/{company_id}/project_regions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds pagination details and endpoint info, enhancing transparency.

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?

Two concise sentences front-loading purpose and usage, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple tool with good annotations; description covers paginated JSON output and metadata, sufficient for selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters (100%), description adds pagination control guidance (page, per_page) and metadata mention.

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?

Clearly states 'Return a list of Project Regions' and expands on usage scenarios (enumerate settings, find IDs, filter). No sibling tool overlaps.

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?

Provides explicit contexts for use (enumerate settings, find IDs, filter) and mentions required parameter; lacks explicit exclusions but sufficient.

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