Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_projects_v1_1

Retrieve and filter construction projects from Procore by status, name, date, or custom fields to manage project portfolios efficiently.

Instructions

List projects. [Core/Portfolio] GET /rest/v1.1/projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesUnique identifier for the company.
pageNoPage
per_pageNoElements per page
filters__by_statusNoFilters on project status. Must be one of Active, Inactive, or All.
filters__nameNoFilters projects to those matching the given string.
filters__project_numberNoFilters on project number.
filters__created_atNoReturn item(s) created 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 `YYYY-MM-...
filters__updated_atNoReturn 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...
filters__origin_idNoOrigin ID. Returns item(s) with the specified Origin ID.
filters__idNoReturn item(s) with the specified IDs.
filters__syncedNoIf true, returns only item(s) with a `synced` status.
filters__vendor_idNoReturn item(s) with the specified Vendor ID.
filters__is_demoNoFilters on project is_demo attribute, which indicates whether project is for demonstration purposes.
filters__custom_fieldsNoJSON object returns project with matching custom_field_values
filters__templateNoFilters on project template attribute, which indicates whether project is a template
filters__by_owner_typeNoReturn item(s) with the specified project owner type ID(s).
filters__by_departmentNoReturn item(s) with the specified department ID(s).
filters__by_regionNoReturn item(s) with the specified project region ID(s).
filters__by_officeNoReturn item(s) with the specified office ID(s).
filters__by_programNoReturn item(s) with the specified project program ID(s).
filters__by_stageNoReturn item(s) with the specified project stage ID(s).
filters__by_typeNoReturn item(s) with the specified project type ID(s).
filters__by_bid_typeNoReturn item(s) with the specified project bid type ID(s).
viewNoThe view determines which fields are returned. 'ids' return only id as an Integer (it additionally influences 'per_page' value to be strictly 200000), 'compact' returns only id and name, 'normal' r...
sortNoReturn items with the specified sort.
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'List projects.' which implies a read-only operation, but does not disclose pagination behavior (implied by 'page' and 'per_page' parameters), rate limits, authentication requirements, or error conditions. The description lacks essential behavioral context for a tool with 25 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise ('List projects. [Core/Portfolio] GET /rest/v1.1/projects'), which is efficient. However, it is under-specified rather than appropriately detailed. The single sentence is front-loaded but lacks necessary content, so it does not earn a perfect score.

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 complexity (25 parameters, no annotations, no output schema), the description is inadequate. It does not explain the return format, pagination, filtering capabilities, or error handling. For a list operation with extensive filtering options, the description fails to provide the context needed for effective use.

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?

Schema description coverage is 100%, with detailed parameter descriptions in the input schema. The tool description adds no parameter semantics beyond the schema. According to the rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description. The description does not compensate or add value here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List projects.' is a tautology that restates the tool name 'list_projects_v1_1' without adding specificity. It does not clarify what 'projects' are, what scope is covered, or how it differs from other list operations. The bracketed '[Core/Portfolio]' and 'GET /rest/v1.1/projects' are technical details that do not enhance purpose clarity for an AI agent.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., 'list_projects', 'list_company_projects', 'list_companys_projects'), there is no indication of context, prerequisites, or distinctions. The agent is left with no usage instructions.

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